As explained in the Technical Design, it should be redundant to emit a 'c' invalidate oplog entry when cloning collection metadata on setFCV (SERVER-127532):

The CSR is either already up to date with what we are about to write (it was populated by the 8.0 catalog cache loader prior to cloning) or is kUnknown. Emitting an invalidate would trigger a full refresh, unnecessary and expensive.

This ticket should implement this requirement. We should also evaluate if there's any other unnecessary/redundant logic during cloning.