Disable when a PURL Modifier is active for a path

I'd like to use Global Redirect in conjunction with PURL, but each to handle different parts of the site. On my site, PURL is active for some parts (restricted areas), and inactive for others (public areas). Global Redirect takes URL aliases prefixed by a PURL Modifier, and strips the PURL Modifier, which breaks my site's Contexts.

There are several related issues, all of which are pretty complex: #346911: Redirect Loop and custom_url_rewrite ignored, #774950: Incompatible with hook_url_inbound_alter(), #900622: Redirect loop cause if $_GET['q'] is changed by custom module..

I needed a simple solution, so I just added code to Global Redirect to disable itself when there's an active PURL Path Modifier.

Does this conflict with others' usecases? If not, could we consider applying this to globalredirect-6.x-1.x?