Most of the points I would bring up have already been discussed. At first I was against the idea because my first impression was that it would actually hinder the dissemination of custom maps. But seeing as nothing would change other than certain maps becoming "required" downloads I see it as a means to introduce custom maps to an audience that may not otherwise take interest in them. Perhaps once they see the benefits, quality and fun of custom maps, they would actually stay and download one from a re-direct.
Afaik, the version mis-match problem is now moot with re-direct downloads. The files are placed in the cache and if the server files don't match the player files the files get over-written. Not so with SWS.
I don't think custom map quality (in RO2) has ever really been an issue or reason to not play them. In areas that have download caps, I see where custom RO2 maps could hamstring one's internet budget'. However, (afaik) in the US, bandwidth limitations (other than speed) are virtually non-existent and not a valid argument against RO2 custom maps. Here in the US, its more a matter of ignorance, impatience, or the erroneous assumption that all custom maps are crap.
Admittedly, there were/are a few newer mappers that cranked out beta after beta after beta instead of taking their time and releasing betas with broad and sweeping fixes. Speaking as a server admin, when a mapper starts cranking out betas every couple of days , I hold off till its a bit more stable. Another unsolicited tip I'll pass along to budding mappers.... don't make your map 45 minutes long unless/until its really necessary or its very close to a release candidate. Other than those two issues, I've found the vast majority of custom RO2 maps to above par quality. Kudos to the mappers.
Question. With this system, once the QB puts their stamp of approval on a map, whose responsibility does it become to re-cook it when necessary? If left up to the mapper and should he no longer be interested in RO2, what affect will an out of date map have on the player if/when he joins a server with an newer version? Likewise, should a patch "break" a map, who recodes it?
Lots of things to ponder. Its not a simple plug 'n play fix.