Currently, the slotClass callback is triggered on every change detection, which also includes user interactions such as dragging or editing an event.
This will become problematic if there is complex logic in the callback and it can get a bit worse if there are bigger slotDivisions in place.
Example with dragging and editing:
While dragging, the slotClass will fire multiple times, and while editing every keypress will trigger the callback. This can be further improved and limit when the slotClass callback is called in the Scheduler component.