This doesnt make sense. The tests that the developers go through while working in a position are the meaningful code that they produce. There cant be anything that measures the impact of a developer other than the actual, real-life production code that actually serves real business cases. Bringing in the tests that don't produce anything that will not be used by anybody into the normal work process would not only be pointless - it would also alienate developers since it's not meaningful work. Its not discovery, its not even research.

The solution to the pointless interview tests that are disconnected from reality is not bringing them to everyday work. It's changing the interview format.