Interesting feature but no at the moment it does no support any
concept such as toBSON
It would create a potential mismatch when you retrieve the object
again for reconstructing the object after retrival as you would have
reconstruct the concept of a private property.
JSON.parse/stringify is incredibly fast by many factors over BSON due
to magic going on in V8. So I would think it will still work much
better and the BSON parser would not have to check for every single
object if it implements toBSON and then handle the additional
overhead.