I’d love to help you out still 
.
See if you can find where in the plugin most computation time is happening and we’ll see if we can work on some improvements. Let me know if you haven’t used a javascript profiler yet though as I don’t know your experience.
I started with column resizing only because it decimated performance with that one handler for large tables (but the PR is just reducing transaction on mouse events not table selections which require expensive ones that might be throttled as well in a similar manner).
There are likely a few more hot code paths that could be optimized beyond this as well.