Of course if you're trying to measure how quick someone can pickup a framework or if they're capable of "hitting the ground running" on arbitrary framework X with arbitrary existing codebase Y with deliverables/output that assume no learning curves while having no desire investimg in long term talent retention, this approach isn't for you. If minimizing time to market is your main goal, this approach isn't for you. If you want to produce something different where time to market can still reasonable but a bit slower, this approach may be for you.
The right tool for the right job AND shop, or you end up with a major maintenance nightmare.
I say indirect because I do not see any evidence of any firm hiring this way...yes MS has stories of hiring someone based on CS or Math level skills BUT we are at a place in time where in fact due to emphasis on UX and cognitive science where Liberal Arts skills is a more important gauge of learning abilities when facing new frameworks and challenges. IMHO
Because any developer with a breadth of experience and a solid foundation can instantly see the intended use cases for said toolkits.
If you've written everything in X then ensuring that your next project is also in X (even if X isn't perfect for it) has many advantages. Your bus factor is high since your whole team is familiar with the technology. There are fewer unknown issues that you'd hit versus a new approach. You'll be able to re-use already written code so getting things running will be faster. There'll be fewer drawn out arguments and discussions on technology choice at every juncture. There will be more eyes able to properly review the code and choices made.
Hiring and overarching technological decisions are as much about business as technology. I've seen many engineers hired who want to rewrite everything in Y because they're not familiar with X. The business gain of it is negative but they still push for it.
I'm not saying that hiring only X is the best choice all the time but rather that a middle ground based on the specifics of the business is necessary. A flat out decision to never hire explicitly for X is as blind as one to without thought always hire for X.