Also, did you randomly guesstimated that you can simply enumerate the keys faster (whatever that means) and straight up go from 4-5 to 5-6? On what basis? Let me tell you the truth: what you said is already done, but you probably use the wrong code or app for this, because an RTX 4090 is capable of doing 7.0 - 7.1 GK/s to scan a given range, not 4 or 5. Yes, just the keys in a given interval, not the ones with symmetry or endo (in that case, it can surpass 10 GK/s).
I wrote it that way because I never run my RTX 4090 at full power, given the extremely low chance of success. When I tested it at 100% load, both the GPU and memory heated up more than they do during gaming or even FurMark. In this mode, the 4090 could overheat and fail rather quickly.
However, I’m not a proponent of prefix-based searching—I’m simply interested in maximizing the search speed while maintaining a reasonable GPU load. Perhaps I don’t fully understand how programs like KeyHunt and BitCrack work, and the key search is already implemented using H160 rather than the full P2PKH address. However, the command in the batch file appears to be searching by the full address rather than its H160, which is why I had this question.