ADB "helper" Service/proxy

For some time I've been using tasks & associated Termux scripts from enable_adb_wifi_on_device_boot_android_11 to enable ADB Wifi on my phone following a reboot.

Since upgrading to Android 13 the task dependent on Read_Logs doesn't work (without relying on ADB!) so I've made an additional task (triggered by VolDn) to read input fields via AutoInput, parse for IP:port, and pass this to the Termux script to connect to the IP:port presented and enable ADB.

Because over time more Tasker functionality seems to need a reliance on ADB (Read_Logs in Android 13 being prime example) my thought is to have tasker run an ADB "Service" (similar concept to Shizuku, also similar to what Helium does, see helium-desktop.sh).
An additional advantage of this could be that once enabled (following reboot) ADB could be left disabled (lower security risk, also less issue with changing networks etc.), while ADB Wifi tasks (along with internal Tasker functionality) could be directed to the service that would maintain ADB permissions.

My high-level thought for approach would be for Tasker to take control of the pairing functionality (similar to Task+Termux script, reading pairing code from screen), and when paired to enable connection to the IP:port presented, and intiiate the service (with ADB permission), then disable ADB/Debugging (if possible without killing the service).