It's to ensure that you, the user, know when the boot process has changed substantially, and that you have a simple way to get back into familiar territory.
If you want to get rid of Chrome OS and all its user protection measures entirely, that's possible with official and relatively standardized means. The open source firmware community provides documentation and tested firmware images for that (of course: no warranty), most prominently https://mrchromebox.tech/