The shard server op observer parses updates to config.cache.collections and config.rangeDeletions to maintain in-memory state about the routing table. See here. This code will need to be changed to handle both the $v:1 update format and $v:2 update format.

The config server op observer appears to have logic which will need similar changes.