There's no real reason for this, except abstraction - we're moving all Template related code to the templating module. In fact, one might argue that there's no reason for the AggregationState to even hold the template node. If a custom module would want to change the template in use, it might as well change the RenderingFilter instead of modifying the data in AggregationState.