You're very welcome,

Speed set the Voxel size for the time of exploration as large as possible. Keep in mind that between 10 cm and 0.1 cm, the difference in amount of voxels is around 100^3 or 1,000,000. This is super simplified, but keep the values for the size large (Low amount!) and go only smaller (Higher!) when needed.

Perhaps download Cinebench and google for results to see how your setup works comparatively. An activity Monitor or Task Manager allows for some exploration if the system reaches a limit.
Switch off all apps and functions that eat into your performance. Google is typically one app that asks for a lot of performance. Enabling redshift only when needed is a current circulating tip.

Please remember that tutorials can be recorded and sped up, then the commentary is placed on top. The tutorial should be slower, as the screen recording is active at the same time.

I do not want to go deeper here, as this forum is not about hardware. But perhaps I have to suggest at one point to have an Ask The Trainer show about performance optimizations of hardware stuff.

However, as a friend told me three decades ago when he got his first NeXT system: Whenever something gets faster, we put more options in our software and have it a little bit slowed down in return. I feel that is not so much different these days. Of course, the primary trend is that everything gets faster (Silicon and code), and expectations might run hot at one point.

All the best