move/merge/split operations use ShardingState::refreshMetadataNow, reloading the entire chunk metadata ~2 times per operation. I suspect this is very costly for collections with large numbers of chunks.

ShardingState::refreshMetadataNow and ShardingState::onStaleShardVersion are the only two exposed means of refreshing the chunk metadata. Only the latter attempts to do incremental load.