Having a separate bond for production and for crossover/DRBD communication should be doable (might need to make it from CLI); i.e. bond0 for management interface and bond1 for crossover. However, I would generally avoid using the same bond for both purposes.
However, using static routes to separate management interface from data collection interface (which I am assuming would happen here) is discouraged - see QRadar: Static route configuration .
It might be allowed (i.e. not impeding your break & fix support) if IBM's services do a bespoke configuration. On your end, you would need to be very careful to properly document and backup this configuration to be able to revert to it after patching etc.