Well, no, he has a point, and it's exactly what we are already doing with the BIOS. It is non-volatile memory that was originally designed as a low-function bootstrap facility, capable of just enough function to get the computer started (load the OS and branch to it).
Modern BIOS facilities do a lot more (RAID, security elements, boot order, and a host of other tasks). It is quite easy to migrate system specific read-only functions and data into that environment - at the expense of generality of the BIOS. Functions placed there would, ideally, be used by any OS the machine is designed to host, and/or there would be a proliferation of OS-specific BIOS products. Not necessarily a bad thing, but I suspect the manufacturers would not find that approach to be financially viable.
Furthermore, OS updates would have to use non-volatile memory modification techniques, such as are currently used for BIOS updates, to install the changes. Without going into detail, such changes are currently risky, slow, and energy-consuming.
Bottom line: Doable, but probably not worth the effort financially or from a usability standpoint.