I however suspect that such an organization, happy to meter the development, would not meter the efficiency of the whole, and especially would not allow comparing that whole to some other organizing model -- it could prove that the managers are the weak point after all.
Most businesses don't have access to top talent and they know it. Most businesses are specifically trying to create an environment where devs are interchangeable, and optimising their processes for the 50th percentile dev (if that).
If you do your measurements within that context then of course 10xers don't exist. But when it's John Carmack vs Scrum Legend #34598295 1v1 on Final Destintation with No Items, I know who I'm betting the house on.
I don't believe it's a matter of finding talent, but a matter of learning it, and you learn it by doing.
The problem is people will only learn skills they need - so if they don't need the skill to be 10x developer, because the management doesn't expect it or doesn't give them the autonomy, then they will not learn it.
And of course, learning something as well goes against short-term expectations of productivity.
If you control for this autonomy, by assigning them small "routine" tasks, then of course the effect is lost.
The paper somewhat advocates an approach to SW development that can easily result in this. If you give people lot of small tasks to be done, they will never be able to articulate that they are actually all very similar and can be factored out into an abstraction.