Headings are the major way people using assistive technologies can skim a page and navigate around. I think a <header> will still be treated as a landmark, even if it's inside other landmark elements, but it will be nameless so not nearly as useful.
It can be a struggle for some people in some situations to create pages with a heading level hierarchy that accurately reflects the content. Sometimes I think when there's any difficulty, authors should basically give up and follow a simple guideline: have one <h1> that says what the page is about and use <h2> for all the other headings.
The words put inside the headings are far more important than the accuracy of the heading level.
Edit: looks like that’s basically the WAI approach too, in that role=heading will default to aria-depth=2.
Using <header> elsewhere for developer convenience is fine but that's all it is.
Headings are especially helpful for screen reader users are especially helpful but their value for sighted users are often underestimated. Developers think that by putting something in a box and by its styling that people will understand what it is, what it's for, when using a heading to put a name on it would be very clarifying.
and for screenreaders this will work maybe sometimes inconsistently. I hope visual llms solve it for our brothers and sisters with special needs. ( and for webscrapers)
BECAUSE THIS NONSENSE IS NOT SOLVING ANYTHING FOR ANYBODY