In a non-multi-doc transaction, when the user operation that causes the multikey field to be set gets batched with other operations during the secondary oplog application, the secondary sets the multkey field with the timestamp of the first operation in the oplog batch.

One option is to derive the correct timestamp the triggering write uses. The other option is to put the triggering write in a new batch, so the existing mechanism will use its own timestamp.