We currently do not parse the user-provided values for secondaryThrottle and writeConcern in the moveRange command. This would imply that we populate _writeConcern member in the migration destination manager at destination shard with local write concern (w:1) by default, which is effectively used in the batch inserter to wait for replication after cloning documents at the destination shard. This {_writeConcern} is passed on via  ChunkMoveWriteConcernOptions::getEffectiveWriteConcern which returns kWriteConcernLocal if secondaryThrottle is off.

The user provided writeConcern without enabling secondaryThrottle wouldn't have any effect in document cloning similar to moveChunk but we don't call this out in the moveRange docs.  This needs to be updated as well.