The way I see it, if they're able to trigger a reset routine from a series of on-off signals, they can trigger any code path from it. A base configuration wipe

The way I see it, if they're able to trigger a reset routine from a series of on-off signals, they can trigger any code path from it. A base configuration wipe or code overwrite could just as easily be a call to a separate code process/stack that runs completely isolated from all configuration values and supports the primitive commands that you'd need anyway to configure the device to a deterministic state for your use case, or update the firmware, etc. If you're able to configure the device in the first place, you're able to trigger it again since nothing on that code path ever changes, has persistent state, or reads configuration values.