I agree completely, I think this is really the distinction that is lacking when people talk about superstar developers. Most aren't developing much of anything in terms of raw implementation, they're redesigning existing architectures, theorizing new approaches, bridging domains, etc.

Those skills are often tied to specific domains that are not quickly transferable so what talented engineer A does efficiently or makes them a superstar is specific to engineer A. Talented engineer B probably does something a bit different or has their own sets of expertise they're superstars at.

There are a lot of misguided organizations hiring on the wrong premise though, that there are developers who just churn out implementations at 10-100x speed so they can reduce their workforce. What they should focus on is engineering talent that makes sure they're tackling the correct problems and focus on the right solutions to those problems as opposed to something silly like developer velocity.