Worth adding, where throttle and debounce can be very useful is in the case of events that trigger remote resources via either websocket and/or fetch calls. Beyond this, secondary effects dealing with mousemove/over/out are another. In the case of render effects, using the nextframe apis with your mouse events is a good idea. Keeping your last mouse event values, combined with a single hook for requestanimationframe.
https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame