Button-y interface can be handled on basically any IO-heavier 8-bit microcontroller with some muxes as all it needs is to handle interrupts and emit event messages over whatever-bus. The solution can even be hard real-time if there is such requirement.
Touchscreen will probably run atop whatever OS powers infotainment system. In theory touch events CAN be handled on the same 8-bit uC, but converting click coordinates to button-press messages requires knowing what is visible on the screen, which either hinders expressiveness of touch interface (fixed islands for controls) or complicates implementation (constant updating of element-coordinate maps). The moment safety-critical control runs along with non-safety software huge validation challenges arise - the performance characteristics of the whole system, including UI, must become at the very least bounded.
Hard button solution can be internally commoditized, whereas soft button solution requires constant babysitting throughout development lifecycle. One is much more expensive than the other, however, once the move is made incremental cost drops dramatically.