Duckeenie IMO has got it right.
A database (something editable, like a .txt or .xml) could be generated using the filenames as they are now (and the MAME rom descriptions). Once it's generated, you can leave it alone or you can get editing. That way, surely everyone's happy and the idea of keeping the rom names up-to-date is placed on the user and not the developer.
What would be needed then, of course, is a way to re-scan the folders to re-create the database(s) for the systems.
I can see two ways of getting this to work:
1. There's one database file (or several for each system). It's generated by mGalaxy according to user demand. If you make amendments in it then mGalaxy will automatically show the changes. If you re-scanned your roms (essentially creating new databases) then you would either have a way to determine what's been changed and leave it alone (a flag in the XML perhaps?) or the re-scan will simply overwrite what was already there.
2. There's one "custom" file (or again several for each system). It's created by the user. mGalaxy uses it's own methods for determining how to name the files, as it does now. If it finds a custom file it checks this against the filenames it has and does a simple substitution.
I think the upshot is that the developer doesn't have to do much, other than provide the tools for the user - they can then amend or leave it as it currently works.
To be completely honest, I'm not that bothered either way. I thought if it is something that users want, then it doesn't have to be a painful job to implement. I'm just happy after trying lots of different frontends to find one that's simple, works and is pretty to look at!! So congrats to the author for doing an amazing job! GameEx, Hyperspin, Mala and all the others have their place - but for me this is the best frontend I've had the fortune to stumble across so far! =)