It's important to remember that the timeout gets reset after the component is updated. Normally, this doesn't happen too often and you usually load the current data set from the server.
If you see that it doesn't get called if you set the interval to more than 10 second it suggests that you refresh the component every 10 seconds using another mechanism: e.g. you have another setInterval() in place which refreshes a text on page. In React, if you include the Scheduler and other elements in a component, everything in the component (including the Scheduler) will be updated when you update any of the elements.
The solution is to wrap the changing part in another component, like in the following tutorial:
https://code.daypilot.org/76269/react-scheduler-how-to-search-events
The max count is introduced intentionally because the auto-refresh is not an optimal solution for checking for changes. You should try to replace it with a something like WebSockets and only update the Scheduler when the server sends a change.