Gaming was fine on Threadripper. The issue was cost. You could get a 1900X for $200 when X399 was new and those MBs were like today's boards in price but so much better in flexibility. The issue is that the 5950x blew the 2920X away in CPU performance so if you wanted that you had to sacrifice PCIe joy and go back to AM4.
Cost was a large part of the problem, another was the availability. The Zen 3 Threadrippers (59xxWX series) was initially OEM only, it took a while before they showed up in retail channels, and even that wasn't available in every country. It also released very close to Zen 4. They need to get their act together and release these together with their Epyc counterparts.
Another aspect is the difficulty of benchmarking "workstation workloads" in a fair and representative manner.
Benchmarking games or large batch server workloads are by comparison "easy" to perform, while a typical workstation is used for mixed workloads. Whether we are talking about "power users"/prosumers or actual professionals (small business owners or in a corporate setting), and whether the workloads consists of development, CAD, modelling, graphics, video, etc., they pretty much all run many different applications at the same time. Not with high load, of course, but different applications "competing" with medium loads are more typical. So what people usually need is something with a decent mix of (consistent) CPU speed, memory bandwidth and PCIe.
I can probably count on a single hand the amount of "professionals" I've seen who only run a single application at the time, and then close it when switching between tasks, the more typical use case is a whole lot of applications open and users switching between tasks during the day. Even for developers (which is my area), there is typically multiple development/debugging tools, a web browser with 100 tabs and a couple of VMs etc. running simultaneously, closing and opening tools would be very unproductive, so a pure code compilation benchmark doesn't reflect the actual usage.
And I believe for those heavily into video editing, I don't think those spend their time watching their videos encode, and if they have the volume for it, they have a dedicated server for encoding and a workstation for actual productive work, so once again the typical benchmark doesn't necessarily reflect the actual workflow.
So I think part of the "problem" which makes the 16 core mainstream CPUs seem more attractive than they in reality are is the choice of benchmarks. Not only is there a focus on synthetic benchmarks (which are pointless for real world usage), but also the weighting of either batch jobs and/or workloads that are too niche. One good example of this is Cinebench, which is probably the most featured benchmark in recent years, and while it is a real workload, it's only relevant for users of Cinema4D. This also becomes a problem if people use aggregate benchmarks to pick workstation parts, as they might actually pick an inferior part (or miss out on the advantage of a better one).
But I don't have the solution of how to benchmark workstation workloads more
fairly either. It's a tricky one. Despite not having used Threadrippers, I can attest to the night and day difference in user experience of working on Intel's HEDT platforms (x299 and x79) vs. their mainstream contemporaries, and I have every reason to believe Threadripper would have similar benefits.
I lament that I cannot justify buying TR today but I do enjoy the special effects in Movies that TR introduced.
While I can't speak for your usage, if anyone keeps upgrading systems due to either memory or IO limitations, going for a Threadripper (or Xeon-W) might actually aid in the system's longevity. Not to mention workstation motherboards in generally are better designed.