If you use cluster and then lookup it should match to the release group in Picard. Then you are a single right click away from checking that it’s the right version.
It’s not as automated as we would all like, but let me stress that even if Picard did some extra wizardry with cat no’s from cue sheets I would still always check the versions for every album when tagging. There is no automated system or program that will be able to deal with the duplication of this data on popular albums, mistakes in printing or manufacturing, or errors by users who’ve entered the data into the database.
But anyway, that one click isn’t so bad, and as IvanDobsky said it definitely becomes part of the fun!
I don’t know enough about CUE sheet data etc, but it sounds like you have a pretty good grasp on it? Unlike other platforms here you are welcome to create a ticket outlining your proposal, or even code/get it coded yourself. It sounds interesting. Not sure if it’s off-topic I always thought pre-gap info would be interesting to store somewhere Maybe there’s a sensible place/way to store your info/strings in the DB (and then these can then be used by Picard). That said, I have to assume that if any of this is the killer app that would solve all tagging issues then it would be implemented already. Maybe there’s an existing ticket? The bug tracker is https://tickets.metabrainz.org
(I think this is where you would report documentation issues/suggestions as well?)
Take a bit to familiarize yourself first though. When you enter or edit a MB release the barcode field won’t let you enter dashes. It also automatically checks and recommends a checksum if you haven’t put that digit/s in (though you can click ‘my release doesn’t have this printed’ instead). I think that was a unanswered question if yours.