I don’t believe they currently have any plans to; MDG has left this fairly open intentionally. I’ll quote @benjamn (from issue 6550):
The official recommendation is that you npm install meteor-node-stubs in you application, which will give you all the usual native library stubs at once. This makes the stubs available to packages as well as your application code. Only the stubs you use will be bundled into your app.
As to why: client-side stubs are fake, partial implementations of the built-in modules found in Node, so you should have the option of installing a custom version that implements your desired behavior. Making that choice automatically for you might seem convenient… unless it isn’t what you need, which is why we let you install your own stubs (while providing meteor-node-stubs if you want to use that).