Imagine you have a geographically distributed replica set with possibly bad connection between nodes. You want to import huge amount of data (around hundred of GBs), which is significantly larger than oplog size. If secondary members can't keep up replicating, they eventually become too stale and transit to RECOVERY mode, requiring manual intervention (initial sync or copying all the data).

If there was an option to specify write concern in the connection wizard (or, alternatively in the import wizard), I would specify it to the number of members of my replica set. That would ensure that the import goes at the speed of replication of the slowest member, never breaking my replica set.