Without a device to test it on myself, I'm not going to change any of the AB-Solution code. It would be guesswork with no end, even if only a small part of the thousands of lines of code need adjustment.
And things may still change, even tho I'm nearing the end of the alpha stage. Broadcom/Asus have caused me a few headaches because Broadcom now uses /opt to store some scripts in the flash, so /opt is no longer a symlink to /tmp/opt, but an actual folder (with a bunch of symlinks inside it pointing to the various /tmp/var/* folders). I had to add a bunch of them to fix Entware. I'm not totally dismissing yet the idea of just scrapping Broadcom's /opt/scripts folder, and reverting to a more natural /opt setup.
So I'd say don't invest too much time implementing solutions yet (exploratory work however is fine).
BTW, I also considered moving HND to Entware-NG-3x, which is more up-to-date and more optimized for newer kernels. Unfortunately, its maintainer decided on a few things that are deal-breakers for me, especially as it forces the installation of Busybox AND makes /opt/bin have priority over /bin, overriding any of the Asuswrt-Merlin own applet. This means any changes Asus and Broadcom made to busybox are then lost, potentially breaking some of the router's core functionalities. The maintainer didn't seem open into changing this, so I stuck with Entware-NG, and focused on getting it to work on HND.