We can remove this piece of code from the rename operation. It was added to solve some problems related to the long names support project, but it was not enough (SERVER-62700). 

My proposal is to remove this code and to decide which kind of filtering information we want to leave on the shards before releasing the critical section. Right now I believe the rename operation leaves the filtering information as UNKNOWN, which is fine and will force to the next operation on the shard to recover the shard version. Another approach would be to call to the forceShardFilteringMetadataRefresh to end up having the right shard version before releasing the critical section.

Note that calling to onShardVersionMismatch will not work because the rename operation is holding the critical section.