I wondered with your doctored binding XML whether the binding would still get hung-up on the Multi_Channel CC and not be able to create the OH zwave node XML (This is used as a storage record for restarts, etc.).
At a high level how, it works; At any startup the binding requests a NIF and the device sends back all the CC’s supported. The binding then proceeds to interview each CC. The device is always going to send the Multi_Channel CC and the binding will always try to interview it.
If you have a 1PM (non-mini) you could create a device from that OH zwave node XML to create a mini XML with the desired CCs for the ZW DB, but my guess is that once the mini sends its “Real” NIF the binding will get hung-up (the reason for my question). It might mostly work (it sounds like you have it working) with your doctored binding XML, but will not produce the OH zwave node XML. Without that I don’t think OH will consider the device fully configured and I’d anticipate other problems (Not able to Heal, etc.).
I’m thinking that a programming hack is needed to temporary allow the bypass of the Multi_Channel CC if versions higher that V2.