Haven't looked at it yet, but very doubtful - they would have to a have a solder pt/jumper clearly documented on the PCB board some how. Could be considered a con to start in Hi for sure.
For power switch UI's, I much prefer the "luxdrv" style of mode changing, where mode changing always starts at the lowest mode, then increments up. I think this is the best way to do it and I think you would prefer this??
You can still have mode memory, even OTC mode memory and use this method - that's what I do now in my power switch firmware. Dr Jones calls it "short cycle memory". I first heard/saw it in luxdrv, but Dr Jones credits BLFer 'sixty545' here in the OP: https://budgetlightforum.com/t/-/4672 for first bringing it up in post #254 here: https://budgetlightforum.com/t/-/744.
My favorite power/tail switch UI is 3-4 mode levels from lowest to hi, optionally followed by strobe and/or battery monitoring.beacon, using OTC mode memory. This way you don't have to click thru the blinkies, but you still can have them. Any more modes is getting into a lot of clicks. Using off timing to act as a 2nd trigger can be done, but can also be vulnerable to heat issues effecting the Off Time Cap, like in TK's BLF A6 - not always though, depends on components, calibration, etc.
Lot of history here, to say the least... We really need to credit Tido going back to 2010 I believe with starting this ATTiny13A programming. This opening post started it all: