More exactly, C code (hopefully MISRA C) generated from Simulink models runs much of the embedded systems in many cars. Although sometimes (cough, Toyota/Denso, cough) that generated C is then bodily assaulted by questionably competent embedded developers until it combines the worst qualities of MISRA C and low-quality embedded development, because, like many low-code solutions, getting (and keeping) everything in the low-code model is hard and the built-in escape hatch to a real programming language is not always a good fit to the problem at hand.

(As a nit, I suspect that Simulink is known and deservedly disliked by the vast majority of people with non-software Engineering degrees, given the omnipresence of Matlab in academic contexts.)

Matlab / Simulink will doubtlessly have a very long tail, but is being overtaken by Python. For one thing, programming is gaining ground in areas that have no established loyalty to Matlab, and those are growing areas. Such as the life sciences. For another, a certain fraction of students want to test the waters and see if they can explore software development as a career option. Python is more relevant to that option than Matlab.

But Simulink does continue to rule its own roost. I think the users see themselves more as engineers than as software developers. And engineers are more inured to using awkward tools.