If Microsoft are the only people seriously interested in maintaining the ability to run Node on ChakraCore as well as V8, of course the team of people working on the necessary abstractions will be mostly Microsoft employees.
Of course, since V8 runs on Windows, not a huge number of people are going to be demanding ChakraCore support - but Microsoft presumably believe they have, or are developing, sufficiently awesome JS runtime technology to make this worth investing in. And it's not like it's worth Microsoft's time to invest in making Node also run on whatever Mozilla's JS engine is called at the moment (I've lost track). But their work on Chakra support presumably would make that a lot easier for someone who wanted to come along and support a third runtime engine.
And it does benefit the whole ecosystem to not be 100% reliant on V8.
JavaScript code and libraries and other web-standards should not be built on a monoculture.
On the other hand we all know what happened with Microsoft had the majority of the JS market share. No need to go back to that.
Microsoft had a chance and they wasted it. They got the keys of the car for a night and they got drunk in it and crashed it.
For R for instance, the interoperability is one-way only. Microsoft R Open can fetch libraries from CRAN, but regular R software cannot use libraries from MRAN.
It's a superset of features, and once you depend on the extended features you cannot go back. In this way you are driven away from the project.
After the "extended" product gains the largest market share, then comes the "extinguish" phase (the end of collaboration), which has been their final goal all along: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
The "vm neutrality" claim on node is very specific to Chakra. I don't see them trying to integrate other VMs as well. Then, node's NAPI team are almost all Microsoft employees: https://github.com/nodejs/abi-stable-node