serverStatus().repl.replicaSetWritesBlockAllowDeletions is initialized to true and only updated from ReplicaSetWriteBlockState after a successful global IS lock acquisition.
If that lock attempt fails (global X held), the default true is still emitted. A node with deletion blocking enabled can therefore report that deletions are allowed.

A part of this ticket, we should initialize replicaSetAllowDeletions from isReplicaSetDeletionsBlockingEnabled() before attempting the lock, so the failure path still reports the correct value.