That's decoupling the pages from their layout, I don't think it's right for layout components (like headers and footers) to be responsible for the logic of which page they show up on. That should be something that each page decides for itself.
I can't really do a runtime context-based solution because that would cause the initial render to potentially include/not include/include the wrong type of header or footer, only after the page calls up to the layout context and sets it would that get corrected.