Overall it's weird that in MeteorLake they only add 64KB L1-I and call it RedwoodCove. So there is a different core architecture in Xeon and it is not RedwoodCove because in Xeon it would be completely different than RedwoodCove. Or it's the same thing, but it's definitely not RedwoodCove+.
It would be an even bigger disappointment if it turned out that ArrowLake does not use LionCove, but the P Core architecture from GraniteRapids.
It's under a different code-name because it's on a different process, even if only has a minor architectural change. Pat has said it's like a + for Granite Rapids. Penryn, Ivy Bridge, Broadwell, all had minimal changes, but different code names because it's on a new process.
RWC on Granite Rapids is obviously not Lion Cove, because it's not wide as Lion Cove is. But this makes sense and it fits with Pat's statement that the move to Intel 3 and a year delay allowed it to have additional changes. They weren't able to fit Lion Cove in there, but they were able to fit more than the client Redwood Cove.
Ultimately the names are not important and tells you little. They called it Goldmont Plus, but a significant gain of 30% per clock.
High resolution shots and comparison with MeteorLake should dispel doubts.
Die shots do not tell you everything, because Intel can choose to have it disabled. The Xeon differs in one aspect, which is having the 512-bit AVX512 unit, which the client does not have.
Opinion is one thing, but Intel is telling you right there, the core in Granite Rapids is different. I don't know why there are doubts? Opinions also said Intel was dead after Netburst and that AMD was dead after Bulldozer.