There are a few places in OplogBatcher::_run that access the storage engine, like getBatchLimitOplogBytes(), which reads from the DurableCatalog.

WT may occasionally return WT_ROLLBACK for reads when the cache is full, so this internal thread needs to be able to handle the possibility of a WriteConflictException without it escaping.