Vedeja yes, as I said, completely backward compatible for those that want to continue with putting Keys, Tempos, Capo Settings, Vibes, Flavours, whatever into the Title and/or Artist fields. It's also worth reminding everyone that the Notes field is also visible in Playlist/Song list for adhoc data, so, we now have arguably better places that the Title and Artist fields for data that isn't Title and Artist.
As a general observation, when software gives you a specific place to store specific data, it is usually a good idea to adopt these things. I've worked in the software industry for decades and lost count of the number of times a customer has said "but I put <XYZ> in this location. Now you've <changed it/made some enhancement elsewhere that leverages the dedicated field> and it now <breaks what I do/prevents me from using this feature>". And the answer is always "well, I understand that you have been doing that thing that way for years, and back then there wasn't a better way, but we created dedicated fields for that X years ago.... blah blah.. so your only way forward is to adopt the recommended way of doing the thing...".
Again, because everyone seems to be on a hair trigger these days, I'm not telling anyone what to do, and I'm not saying what anyone is doing is wrong. What I am saying, is that it is generally a good idea to use the features the software gives you to do things, otherwise down the track there could be unexpected ramifications or just the ability not to use (or fully use) certain new capabilities.
Plus, if @peter builds these features for us, it would be downright rude not to use them! 😛