Remote Update of Cyclone 10

The standard solution just doesn't fit that nicely into my application. I just want the factory page to be a fallback golden configuration in case anything corrupts the reprogramming process of the application page. This will then still allow additional tries at programming the new application config data. If I have to load the factory config, then trigger another load of the application config, which if it failed would then cause a third configuration cycle to reload the factory config. This would take extra time to get to a point where the FPGA is operational. It also adds extra requirements on the factory config to trigger the application load and also determine if that failed previously and therefore shouldn't be loaded again. It all just makes it more convoluted and complex. I just need a simple system that loads my application at power on and falls back to the factory config if an error occurs. Is there not a way to do this without the baggage of the remote config as you describe above?