People will say you're burned out, and they're not wrong... but this doesn't address the substance of the issue. To be an engineer or a scientist today means tolerating a lot of the things you've mentioned. I would amend your list to engineers that had a passion for EE and value human life (who doesn't?) but took a job at Raytheon. The things you identify are valid issues. If you're worn so thin you can't ignore them, it has the effect of ruining your entire relationship with the art. The thing to remember is that this is not the fundamental nature of science or engineering, but the nature of practicing these things today under the framework in which we live. From there, maybe you can find places where you can practice your art which are less prone to these issues. You may have to compromise on career stability or pay. People are rarely paid well to do fun, low stress things. Maybe the best thing to do is stay out of tech professionally, and slowly ease back into programming as a hobby by working on small projects. I'm not sure. All I know is that with burnout it's somewhat challenging to untoast toast, but you will recover eventually. It's just always a bit slower than one would hope, but it does happen.

Another angle perhaps is working on clarifying to yourself the ways in which you got hurt, so programming may feel less painful. I found that learning about politics and history-- specifically the history of engineering-- really helped me sort out my feelings. It also gives a sense of clarity of where the rotten parts come from and maybe how to avoid them.