After performing an initial sync, a node will transition to secondary/primary. Transitioning to a readable state (secondary/primary/etc) does not observe/respect the slaveDelay which may lead to user confusion if the node is queried with the expectation that the data is not newer than the expected delay.

Due to the way replication works (that we are copying live data during initial sync, which may be after slaveDelay line) we cannot get to a consistent and valid state without current data.