Thanks for the welcome (and sorry for the late reply)!
I did some more research on this topic and found a solution that worked out for me so i thought i might aswell share it here in case anyone else runs into such a problem.
My guess what happened:
It was indeed a problem in Windows as you hinted or at least it was the root cause.
The Launchpad X gets listed as ‘LPX MIDI’ in the Device manager, no matter how many are connected.
Bome midi translator appearently correctly notices that these were 2 different devices (unlike Novations own software btw) and gives the second one a (2).
My only explaination for the phenomenon that both disconnect when the second one gets disconnected is that it still looks like ‘LPX MIDI’ got disconnected for both Windows and Bome which is why the midi channel of ‘LPX MIDI’ gets closed and bome closes ‘LPX MIDI (2)’ too because it knows that actually this one got disconnected.
My solution:
So knowing that the Name of the Device in Windows is the root cause i attempted to find out how to get around this. I found out that the ‘Parent’ Property in the Device manager properties actually contains the Serial Number of the Pads next to the USB Path of it. Searching for this USB Path (Something like ‘USB\VID_xxxx&PID_yyyy’) in the Registry (I used nirsoft’s USBDeview to find the registry entry) you will find the String entry ‘FriendlyName’ which you then can change to ‘LPX MIDI A’ or whatever else fits to differenciate the 2.
After doing this I was able to properly configure both Controllers individually without problems and disconnecting one of the 2 or switching USB Ports didn’t cause any issues and both showed up with their correct names (Tried this Scenario on different machines just to be sure it works).