Earlier quoted context omitted.
I worked on BMW infotainment for a time. My opinions are my own obviously, I don't even work at BMW anymore. So, when I was working, I found the decisions regarding the infotainment mind boggling, to me they made zero sense, until I found some random documents deep in the BMW intranet, where I found the logic of it all: The focus was actually increasing the car range, so for example instead of having one infotainment…
Isn't what you are describing known as Zonal Architecture (as opposed to Domain Architecture) and supposed to be the hot new way of architecting automotive platforms? Tesla was pioneering it. The Volkswagen Group spent billions to get their hands on Rivian's zonal architecture platform. https://insideevs.com/features/724945/zonal-architecture-sof...
But bafflingly to me, almost zero of my coworkers seemed to be aware of it. They would just get the seemly weird orders from above and would execute them, without figuring out the end goal, and this does result into some bad software engineering (because people don't know the end goal they don't know what they can optimize, so they just don't).