Great question.  The reason was to support the lifecycle order use case that we talked about this morning.

i.e., users may call `add-proxy-route` during the `init` phase, but the server's SSLContextFactory won't be initialized yet.  That means that I have to have something for add-proxy-route to reference / close over during the init phase that will give it access to the server's SSLContextFactory at runtime, after it has been initialized.

I'm not in love with this solution and would be more than happy to consider other approaches if they will still be able to address that use case.