ADO.NET vNext will get there, eventually. The question is however: when. It's still said it will be in Orca's but some doomsayers say they won't make it to Orca's (hence the presense of DLinq on every roadmap, if both were scheduled for release, DLinq have been canned by now).
What MS wants to do is make ADO.NET vNext's core (the entity stuff with eSQL, their extended Sql stuff, of which some statements aren't usable in Linq, so you've to use the sql strings) an element of Sqlserver vNext, and this is also the reason why they're working on it with a lot of people. (I'm told 150 ). Still it won't have the same featureset as llblgen pro when it is released as it looks now. .
It's not the return of objectspaces though, ADO.NET vNext is made by a different team. The ObjectSpaces team works on DLinq (now called Linq for Sql). Now, I'm sure they're all very smart, what I really wonder is why on earth they're so unproductive and progress is so slow for them.
The journalist who wrote the article apparently has no clue whatsoever, OPath isn't used ANYWHERE in ado.net vNext...