On-disk catalog multi-key update for multi-statement transactions happens in a side transaction block.
SERVER-48010 replaced ghost timestamp (determined by logical clock) with no-op write for timestamping the on-disk catalog writes on primaries. Since initial sync doesn't set transaction recoveryPrepareOpTime while reconstructing prepared transactions, it wrongly calls primary no-op write code path to acquire timestamp for the catalog write. As a result, we hit this invariant failure which leads to initial syncing node server crash.
This happens in both 4.4 and master.