Although i am not really able to find the solution as i stated above, i try to analyse the problem - hoping this might be helpful for someone knowledgable.
Is z-wave really blocking /dev/ttyUSB0? To proof this, check usage of an USB-Stick on /dev/ttyUSB0. Does it work?
If it really blocks /dev/ttyUSB0: is this true for USB1 also? Just give it a try while plugging in “something” to USB0 and test functionality → will not work, see above. Check /dev/ttyUSB* just to be sure, which USB* was used and plug in the next USB device. See what happens. I’d expect CC2652RB not to work on /dev/ttyUSB1 also (if it works: ugly workaround).
Whatever the results are: i’d expect them to give a better idea of what/where the problem might be.
From what you have written and what i remember bifi2090 did, i’d expect the problem to be somewhere where @chris (sorry!) already mentioned he remembers “something” (serial communications). The prob seems to be triggered by using CC2652RB for zigee2mqtt and caused by starting z-wave binding (or the other way round). It does not depend on docker, as we know now.