Another problem here that comes up with the proposed solution above is that if we make snapd modify the config.txt for a run mode system on ubuntu-seed, then booting into a recovery system on ubuntu-seed will use those settings as well, so if a user modifies something in config.txt that is i.e. kernel dependent or otherwise breaks something, they can't go back to recover mode and boot since those settings will still be active.
Another problem here that comes up with the proposed solution above is that if we make snapd modify the config.txt for a run mode system on ubuntu-seed, then booting into a recovery system on ubuntu-seed will use those settings as well, so if a user modifies something in config.txt that is i.e. kernel dependent or otherwise breaks something, they can't go back to recover mode and boot since those settings will still be active.