I am still wondering why this site has not reported on this yet?
Anyway, I think this may be looked upon as the death knell for W10M and, whilst it may be. I just think it means that Microsoft IS working on one last reboot of the mobile OS and this is their way of putting the old system out to pasture so that the new system and hardware can be focused on.
At least, that's what I like to think. Knowing Microsoft though, it is most likely the end of it all. But I hope not.
Curiously, a quick google search this morning betrayed a recent Windows Central article on the topic of Feature2 and forthcoming enterprise features, but I found it to be inaccessible, which may suggest it was pulled before publishing.
That said, slowly and surely developers are pulling the plug on apps and app updates, e.g. Runtastic recently announced it will no longer update its apps on W10M. Ouch--it's been a go-to app for me for years (despite the functionality missing on W10M vs. other platforms). Another--Garmin Connect hasn't worked for me since CU. Apparently, we have MS to thank for breaking Bluetooth for many devices in CU (not limited to Mobile).
So, two recent examples demonstrate (1) developers continue to leave the platform and (2) MS isn't always improving the W10M experience. Even if/when CShell comes to the platform we can, I think, expect to witness the demise of a gob of more apps that developers have already abandoned or will b/c there's no money to be made.
Hanging on to W10M at this point feels like hanging on to that one beaten down stock in your portfolio to which you have an irrational attachment and b/c of that you ride it all the way to the delisting. No doubt I'll keep my 950xl until it up and dies, but for me the ride ends June 20.
P.S. I'm not trying to be a nay-sayer, but my life sometimes seems littered with great ideas that MS ultimately abandons. Kinect...? Yeah, it still works, but functionally it's declined since the advent of W10. Is any developer making use of it anymore? (I don't think so.)