It never says so. Maybe you should read it again.
It's basically what it says. Considering that back with the very first Atom(in-order) they tried new ideas, and did it again and again, while recent cores like Tremont, Gracemont, Skymont is wider and bigger in structures than the P core, it's really a bad conclusion. The P core team pretty much stalled since Sandy Bridge.
The Intel cores were criticized by many architects for many, many generations for having tiny L1 caches and little fetch bandwidth. It continues to today. The E cores surpassed those limits back in Gracemont. The P core team is basically expand, expand, expand. That's why it's so bloated. It's a laughingstock and why AMD is kicking them in servers and power consumption in desktops so easily.
Assuming higher clocks on E-cores that are much wider than previous E-core designs is a questionable assumption.
Yet it is according to a deleted leak that says 5.7GHz top Turbo for P, 5.4GHz all core, and 4.6GHz for Skymont on Arrowlake. This core is going to have big ramifications not just for Intel, but based on the Zen 5 reveal, AMD too.
*Who* did *what*? Who/what are you referring to? There are multiple combinations - which combination do you mean?
You. I am referring to you, that said Zen 5 and Skymont is better because of the clustered decode design. It is a compromise to try to overcome limitations of x86 ISA decoding - where traditional increase results in quadratic rise in transistor usage in decoders(hence the neverending ARM vs x86 argument). When it comes to pure decoder performance, Golden Cove's single 6-wide is better. Of course when it comes to overall design as a core, saving great deal of transistors allow you to beef up other areas. And based on Tre/Grace/Sky's results, clustered decode is the way to go.
Skymont is better than both Lion Cove and Zen 5. It means per clock Lion Cove/Zen 5 will be less than 15% faster. Lion Cove is 3x the size with less efficiency. It's a done deal.
Again, it was the E core team that brought the revolutionary clustered decode design. Saying it is done by "removing things" is doing the team a diservice, because it's going to kick ass.