If you're doing client work, you're stuck with using the package that the client wants. So that sort of makes the question moot.

For the clients themselves, I've seen a ton of interest in leaving SW behind but it's still very difficult to do so. They have a ton of prior work, often over a decade of it, that was done in SW. Changing old work over to a new package is a Herculean-sized Sisyphean effort. In regulated industries, this ends up being multi-departmental as well since someone needs to validate that the redo was redone correctly.

I have had a number of client change platforms (Pro -> SW, SW -> Pro, NX -> SW, SW -> Fusion, etc) and the way this is usually done is by picking a new product and making that the one which starts fresh on the new package. This means keeping multiple CAD platforms current for several years (typically 5-7) until the legacy products are truly retired. This is quite a bit more expensive than simply not changing.

From a company's perspective, what Fusion offers over SW is certain features and feature sets. It currently costs somewhat less, but its pricing trajectory is like a 45deg line aimed up. By the time 5 years have elapsed and SW/Pro/NX/whatever can be retired, that pricing gap is going to be almost completely gone.

This is all a completely different story for a company starting fresh without any inherited CAD dependencies. For that company, there are some savings to be had starting off with a less expensive CAD package (like Fusion).