This gets repeated every time, and it's nonsense. SolidWorks is mostly single-threaded, but it's also not a demanding application. Even PCs from a decade ago can handle assembling medium complexity models just fine. The few features that are demanding, like rendering and analysis tools like FEA, are in fact multi-threaded.
And if you actually need model assemblies so complex that single-threaded performance in the base app would become a problem, you'd be running a Quadro card anyway, and CPU performance wouldn't matter.
Source: Industrial designer who worked with SolidWorks, PT Creo and Rhinoceros for a while after uni before transitioning to a different area of design.
This is the crux of the issue. People talk about "ST workloads" vs "MT workloads", but the reality is that single-threaded workloads largely do not matter, it's all stuff that, at the very worst, is done after a few seconds. MT performance, on the other hand, can save you hours of productivity depending on what your work is.
We are long past the point where ST performance matters for the "snappiness" of systems. Zen 3, Alder Lake, M1 and newer are all more than perfectly "snappy" in any modern system. Gaming is the last use case where ST matters so long as you have a minimum amount of cores, but for professional use cases there's nothing to even discuss, MT is the only thing that matters.