SERVER-112570 ensured showing low priority ops only if the fixedConcurrencyWithPrioritization algorithm is enabled. This works fine for most scenarios, except if the customer had the algorithm fixedConcurrencyWithPrioritization and dynamically changes to throughputprobing. If this happens, we'll lose traceability because operations that might be in the low priority waiting for a ticket or already holding one will not be reported in the stats. The following t2 screenshot shows the issue:

The purpose of this ticket is to first evaluate if this behavior is fine for the stats, and then, if not, change the code to make sure we report stats as long as there are ops in that waiting set even if we changed the algorithm.