I'd consider folding this into the SchedulerBinding instead of making a new class, as that will avoid introducing more semi-global variables and provides a mechanism for us to override/track this functionality in testing.    