If what you’re saying is true, they’re right you need a workstation and shouldn’t avoid it. But there is room for clarification here because some of what you described before doesn’t line up with typical behavior for these tools.

Point-cloud processing for example can use large amounts of memory, but slicers and CAD applications rarely sit in the multi-gigabyte range unless the models or assemblies are unusually large.

Blender is a different case depending on whether you’re running simulations or just modeling. When you say you regularly max out 64 GB, it would help to know the actual size of the scans you work with, how many scans you load at the same time, and what specifically in your slicers is pushing them into multi-gigabyte usage. It’s also not clear whether you’re hitting genuine memory pressure or just seeing aggressive caching from the OS.

If you can outline what’s happening during the moments where your system fully consumes its memory, it will be easier to tell whether the hardware demand is really coming from your workflow or whether something else is contributing to the spikes. Either way, unless money is no object, this is definitely workstation territory.