This tends to make QA a gateway job to dev, SRE, or product management. In some organisations the QA function is perceived as a dogsbody role, and the reframing helps flatten the pecking order. In the long run there’s a virtuous cycle to accessing the talent pool this way.
There should be the same career progression possible in your QA department as any other engineering department.
It always takes longer to write tests than not -- at least in the short run.
Some developers, at least, seem to get it now. Even if they don't write enough tests, they have some awareness that they should be writing tests.
Ops? There might be exceptions, but most ops folks don't even think they should be writing tests. And yet, many ops folks do more automation than before, write more code or complex config.
I agree there is no easy fix. Changing minds is always harder than finding a shiny tool.