thanks for asking! It’s definitely not exactly intuitive behavior, but it’s by design. The list of MIDI devices you see in the web config are assembled from
1) real MIDI ports (e.g. Faderfox PC44, BomeBox DIN, etc.)
2) auto aliases (Network 1, USB 1 – USB 5)
3) aliases (I assume Fastlane and others in your list)
Auto aliases are created automatically for each USB port and for each Network MIDI port so that you can access these ports by number (no matter which device they actually represent) in your MIDI Routes (and route sets), and in your MT Pro projects. So you can set up routes to always route BomeBox DIN to Network 1, no matter which Network MIDI connection you have set up in this case: KTBK). So you have the choice to bind your routings to a named connection or to a generic device by number.
“Normal” aliases cannot be created in the BomeBox web config, but in MT Pro projects. In th MIDI Ports page of the BomeBox web config, you can then define which alias from a loaded MT Pro project is assigned to which real port. In your picture above, you can see which alias is assigned to which real port in parenthesis.
I hope that makes a bit more sense! The BomeBox user guide also briefly discusses the auto aliases.