The situation with Futaba 2.4GHz is that the affected TXs and TX modules did indeed suffer from a design defect. The defact was such that a rapid power cycle could set the TX "unique" ID (UID) to a common value of zero, thus ensuring that two TXs suffering from the symptoms will interfere.
AIUI Futaba have performed a redesign (of the software) which ensures the problem should not recur. The fix can be applied to existing TXs which requires they be sent back to the local distributor/importer.
It *is* a common logical channel as the channel selection mechanism for fhss is code division medium access control. Ie the channels used at any time are determined by the TX UID.
I don't think anyone here was Futaba-bashing. However there was a problem and the Futaba importers' responce differed in different countries.