Since my command station (Intellibox) also supports LocoNet and seeing how prevalent LocoNet is, I decided to take a look and see if there were any advantages over my existing command set (P50b of the IB)

Here is what I found:

https://cabin-layout.blogspot.com/2018/07/LocoNet-Intellibox.html

I fell into the LocoNet option in the 90s when the various groups I was involved with picked different controllers for their different purposes.

My first project was a train controller mirror which would, theoretically, allow interoperability. Locos had the issue of converting 14speed stepos to 14,27,28,128 and laterly 1000 AND controller improvised acceleration/deceleration , however for accessories it is a no brainer.

Loconets obvious benefits was its peer<>peer and bidirectional communication. Thus , with a simple RR-Circuits, Serial<>LocoNet (now USB<>Loconet) adapter, any "old" PC could become a remote track control board WHILE ensuring the other control boards were kept in sync!. I still advocate a "small" solution for Track Control with 6021 and uhlenbrocks 6021<>Loconet adapter for its ROI

Of course Uhlenbrock had their own adapter , but they also provided their TrackControl componentry should you wish, like I did on occasions, a tactile solution rather than the Touch options of the time (remember that touch screens have come a long way in 20+ years)

In this sandpit we also have the Faller<>Uhlenbrock relationship and the Faller control module with a) Loconet adapter b) Sensors c) switches is a great building block if you do not actually have an IB-II.
On that note I remain a champion for having different controllers for your Locos v Accessories - if nothing else, for power boundary demarcation. Where interconnect is needed (e.g. sensor triggering a locomotive whistle at the tunnel, this can be managed with selective mirroring

Along the way (timeline wise) , ESUs CS1 did eventually provide a workable TCP/Ethernet offering to address the bidirectional limitation of the 605x, but it was never totally complete. The CS2 UDP/Ethernet was a backward step for the modeler and recreational programmer - and is still not 100% although other bells and whistles have been added. When the 60128 came out with its RJ12 connector, the ears pricked up that this might imply Loconet, but that hope was bound for the dumpsite. An ECoS(systembus) to LocoNet adapter does exist which I have not had direct experience with - AFAIK this will not work with the CS2/CS3

Currently my interest remains in accessory and sensor management with display screen visualisation, although I have spoofed LISSY devices to have the TrackControl display loco-addresses for those that do not have LISSY tranceivers. For this you may sniff the loconet as these commands are not in the Digitrax doco, but Uhlenbrock does have some data on the extension. That said, I havn't monitoed the JMRI forum for about 10 years and they will have moved on.

yes, indeed, the slot management would add some additional complexity.

I already maintain an array of all my locos, so I would have added a slot number property to each loco. Then one needs to monitor all the slot move commands and keep things up to date. As you say then request a new slot if a loco does not have one.

I think that another system such, BiDiB also has a slot allocation system.

I did see that openDCC has a controller called the Z1 which has a mode that not only emulates the p50b command set of the Intellibox, but also extends it!