no they are rendered with a twig function. but one way to work around performance issues would be to make that piece an ESI block to cache it, so its definitely a scenario. but then i don't know how it would work in a sub request. not sure if its even possible to have the master request and a sub request in the same context or if a new one is started anyways.

we could just drop the check here and say if a service only wants the master request, it could make its setter not overwrite the request if its already set. i guess its safe to assume the master request is always the first one...