How about custom config url rules, how will your hack parse the url rules for frontend while being in backend ?
Say i have a rule like:
controller/x/y/z => 'site/x'
In this case, the hack, will in best case generate, instead of say, /admin/controller/x/y/z the /controller/x/y/z route, which is wrong, because the needed route is /site/x .
In the above example, there is no other way, than to have the rules in the common configuration so that when the url is parsed from backend, the URL manager becomes aware of them and knows to generate the admin/site/x route and later strip the /admin/ part from the generated route(the strip can be done with your hack in this case).
BUT, i still end up sharing url rules between apps, so in this case, why complicate extending the url manager and create urls in the application using something like frontend:/route/here ? This might pose problems when you decide that your hack isn’t good or for any other reason, you decide you want to stop using the hack.
Dunno if you really see my point here, but the fact is that your solution, like mine, doesn’t work as we would like, and there is no way to make it work unless the url rules are shared between the apps.
L.E:
It makes me curious, why when they wrote the wiki article they didn’t touch this issue ?
And also, it would be nice if one of the developers would leave his input here.