Most people designing IoT are NOT CompSci people who remember Therac-200 in class. Most are EEs who often have never had more than one or two programming classes and often often have had no formal training at all. Never mind "security theory" courses. Never mind case studies around that.
It's like expecting the average man on the street to be able to perform brain surgery.
Worse: no employer is willing to pay for the talent to do the job right. They want it to "work well enough" and "on the cheap" at the same time. Once it's sold, any security issue is someone else's problem (even if it's someone in the same company).
And I'm saying this as a degreed EE (I just happened to get into software long before I went to engineering school so I know what I don't know).
We now have things like platform attestation that - unless your adversary is a state actor - stops some physical attacks.
(Not available rpi right now, but maybe in 4-6 years?)
Raspberry pi's might not look professional but they are easy to procure and develop with whilst only adding a small amount to a BOM. Even when using a different SoC very few will be setup to use a fully secure boot process.
The original vulnerabilities found were mostly in the web apis of the servers that these chargers connect to which makes vulnerabilities in the hardware irrelevant.