Yes, that is a good point, I have not seen this being mentioned in any tutorial, YT video or alike. Probably because classical is not really a priority for many listeners organizing their local library (to be fair, Hans is mentioning it frequently on YT). I personally had to use a lot of try&error although having vast experience with digital formats and metadata as well as musicological data such as opus catalogues of the important composers.
Roon´s musicological features are so mighty and at the same time difficult to fully overview and handle as several database concepts are intertwined here (performers discography, composer´s discography, track lists, opus lists, recording lists and alike). At times the underlying metadata is not consistent enough to fully serve the purpose, for example I am struggling with this complete/incomplete flag currently as I have a lot of operas and oratories (if I recall it correctly, you had also metadata-related issues).
I think you are right in terms of easy-to-use frontend and search logic which are both not really intuitive. On the other hand you have a multi-dimensional database, and necessarily page for every type of entity (performer, composer, composition, recording, album, track) will look differently if you use all underlying metadata and intertwine it.
So, after some time of getting used to it I think it’s astonishing from musicology point of view. A bit more adoptive in terms of bad metadata quality (which is not roonlab´s fault) and some more explanations - voilà, it could be the greatest tool for classical music!