1) Best I can think of is to maybe provide a static wrapper? something like SystemRewriteDriverFactory::InitApr().

An another alternative is to just call it again; multiple calls to apr_initialize are OK, though then you probably want a matching clenaup call as well, which will be very hard to schedule generically.

2) re:proceccess. I think they're irrelevant, though Apache will call it pre-fork since it uses it heavily. IIRC I picked this spot because it's right before ChildInit(), which is what creates the fetchers.