And game devs don't care because they already have their own middleware.
You won't find much FOSS software on Nintendo, Playstation or Xbox, and for the respective middlewares porting to their respective 3d apis is cost of business.
Vulkan works only on desktop thanks to the same ICD model as OpenGL, which isn't currently supported on UWP.
Frankly, nobody cares about UWP and nobody cares about Microsoft mobile OSes. Their usage is lower than deskto BSD.
One day those Windows 7/8.x licenses will expire.
Yesterday's Windows Developer day was once again all about the store, IoT and new AI frameworks.
Surfaces and hybrid laptops are also mobile OSes in a certain way.
The licenses won't expire; the support will stop. UWP is not automatic successor, many apps are on Windows because of Win32 and that nobody wants to rewrite decades worth of code. Kill that and you kill Windows.
In Microsoft's plans perhaps. I don't know of a single person, offline or online, who uses UWP. I've seen some UWP apps benchmarked by magazines, that's about it.
I also have anecdote data from our customers doing UWP ports.
The PS 3 also had OpenGL ES 1.0 with Cg shaders as secondary API, no one cared.
Vulkan on the switch isn't a suboptimal implementation at all. It's the same Vulkan implementation provided by Nvidia (this is indicated by Ryan C. Gordon, who ported SDL2 to the switch, and subsequently ported the Vulkan and OpenGL support). That is a first class implementation, in regards to features and support, unlike OpenGL ES for the ps3. Plus, Vulkan as a low level api works best for abstracting performance, even more so with the features it has for abstracting perf out of mobile hardware like the switch has (such as for example, render subpasses).