The architecture guide mentions

If known problematic operations such as renameCollection are received, where we cannot assume a drop will come and fix them, we abort and retry initial sync.

This is no longer the case for renameCollection; as of 4.4. I do not think there are any such operations – all idempotency issues are resolved by the time the endTimestamp is reached.