Well, except that “no” goes well beyond folder browse capability. See my post here:
The suggestion in my linked post right above yours is basically the same idea. Yours is a little more sophisticated; same general desire.
I can understand the no-folder-browsing mentality as being a deeply-held belief in a better way to browse media. That is fine. But it also means that anyone who invested in organizing and curating their libraries by using the folder method cannot leverage that work within Roon. Means if they want the same capabilities, they have to re-build inside Roon. Same goes for custom metatags within library files.
Rebuilding within Roon, without the way to import from a more inter-operable method, or without the way to export back out to a more inter-operable method, is a way of keeping users from using the competition. That particular aspect has me concerned.