It’s called Chef.
If you have a hardware failure how would you rebuild?
Of course this all takes time to implement and manage -- it's a tradeoff.
Mikrotik routers and switches can boot from dhcp (or bootp?), but yes a typical switch can't.
Not a network person, but I assume you can give fine grained enough control that you can't do a "copy running-config startup-config" on a cisco switch, so have a startup config that boots to a known basic state then tftps it's config from your HA dhcp server.
Why revert it in the first place? Why not deny the changes? Doesn't this indicate that the wrong people have root access?
This just makes you sure actually go back and change the deploy code, else it breaks in ~2 days.