This will definitely be required in 3.8 (or whenever we start routing requests by UUID), and there are already workarounds for change streams on sharded collections and mapReduce with sharded output to read the UUID directly from the config server, since it is not available on the routing table cache.

If we can get this into an early dot release of 3.6, it would simplify some of those workarounds.