Documentation Request Summary:

--setParameter waitForSecondaryBeforeNoopWriteMS defaults to 10 milliseconds. This is the time a secondary node waits before making noop write in the case afterClusterTime specified in a readConcern does not mathc the last applied time from the oplog.

Engineering Ticket Description:

Current implementation if afterClusterTime waits makes noop write immediately after detecting that the requested time is > then available time in an oplog. Instead the wait should be adjustable to avoid unnecessary writes.
Adding a WaitForSecondaryBeforNoopWriteMS parameter and waiting its value will solve it.