There was a rumour awhile back that some engineers at Intel proposed putting Meteor Lake entirely on N3 in the event that Intel 7nm/Intel 4 proved to be inadequate. The plan was allegedly scrapped as a matter of pride. That doesn't mean that any serious work was undertaken at that time to port Meteor Lake over to N3 . . . but it could mean that there is already a faction within Intel that is amenable to the move.
I think you're referring to a story that I told a while back, but it seems like some of the details got warped over time. Back in, maybe 2019-ish, the design teams were starting to hash out what exactly Meteor Lake was to be. They basically told management, "If you want us to compete with Apple, we need to be on the best process, like they are" and looking towards the original mid-2022 production timeframe, that was N3. Management, obviously, was not thrilled with the implications of outsourcing the entire client lineup, and to a cutting edge (expensive) node at that. After some back and forth, and a very questionable top-down design decree, they ended up with more or less the Meteor Lake we see today.
So the N3 proposal was less about delays for Intel 7nm/4, and more just observing that N3 would simply be the better process, even if the original 7nm plans held. Though that said, I think the current
Meteor Lake definition was concocted in no small part as a hedge against fab issues. And most of Intel's design teams have, at this point, no particular love for the fab side. They want something that actually works, as specified, when
Anyway, the design teams may be open to the possibility, but porting RWC in particular is probably impossible in the timeframe rumored, so I think it's easy to dismiss that particular part of the rumor. But I could see merit in the claim that they're negotiating a different product split to compensate for delays.