It sounds like a solution to a wrong problem. Why can't Vulkan / SPIR-V themselves be used for that purpose? Building another level of abstraction on top would just complicate things, and for the sole reason of appeasing lock-in jerks. I.e. while it might work, it's a pretty bad solution, engineering wise.

If anything, Vulkan needs simpler APIs abstraction, something higher level that uses common logic for stuff like memory management and etc. That's actually useful. And not spending time on this. But well, Khronos can do whatever they want of course.

And we'll need to wait and see if the above lock-in jerks will decide to participate this time.