Completely agree about the settings being categorised - in fact I'd be happier if they were nicely categorised in the database, but as it is they're all just glommed into a single table listed in alphabetical order, without any sort of hierarchical structure in the key names (such as you do with objects in firefox's about:config for example) - wouldn't it be nice to have a frontend.display.widgets.renderer = opengl for instance?
Agree that it's entirely possible I'm doing very complicated things, but this is why I get so annoyed at the bulk of Myth power users; I say something's needlessly complicated, and I'm told it's because Myth is so powerful. If something powerful doesn't work as I'd like it to, I'm told I'm making things needlessly complicated.
Technically, there is no ordering of settings in the database. They are just inserted as needed. If they showed up in alphabetical order, its because you sorted them that way in your select statement. Manual tinkering with settings outside the GUI has never been recommended or supported in any manner.
Almost everyone will agree that there are far too many settings, and that their layout could be handled better. MythTV was designed for, and used on for several years, low resolution standard definition TVs. What works there doesn't make much sense on a higher resolution display. I have to say 'almost everyone', as there has been concerted effort over the past year to clear out bad and unnecessary settings. Every time something would be removed, people would pop into the mailing list and IRC channels bickering about how they couldn't live without their particular pet setting. Nevermind the fact that the setting was no longer even functional, and when it previously did function, enabling it caused bad things to happen.