Isn’t this just an effect of a more general problem related directly to the dcc.Iterval component? If the Interval is triggering a callback whose duration is longer than the interval property of the Interval component, the callback will never be fully executed.
Furthermore, if this callback is supposed to disable the Interval under certain circumstances, the Interval will never be disabled and the app will get stuck in a loop. It has been discussed here.