Should applyWrites offer swapRecord options for update and deletion ops?

[DavidBuchanan314]

applyWrites has an optional swapCommit parameter that applies to the whole transaction, which makes sense. However, I think it would be good if there were also optional swapRecord fields for individual update and deletion operations, to match the functionality of the updateRecord and deleteRecord APIs respectively.

By the way, I don't have a specific need for this feature in mind, but it does seem like an asymmetry in the applyWrites API vs the not-batched versions.