Even though we set full:false in the validateCollection test hooks, since we set enforceFastCounts: true and collHash: true, it is getting overridden on the mongod level because we use isFullValidation to check for full validation, not the full option set in the test. This logic makes enforceFastCounts and collHash always imply full validation, so changing the full option on the shell level doesn't change anything, causing the oplogApplier thread to still hit the EBUSY conflict with WT::verify (see linked BF). 

If we think this will lose initial sync test coverage for enforceFastCounts, we can also add a targeted test to cover that gap. This will turn off full validation for this suite, so if we want that coverage still, SERVER-113259 provides another way to get this coverage without hitting this race condition with the Oplog Applier thread.