The new IMU is correctly identified at INS_ACC2_ID and INS_GYR2_ID on the SPI bus. That seems proof positive that the firmware is recognizing it, and the SPI bus shouldn’t be conflicting with I2C devices, anyway.
I recently took delivery of a Matek H743-Mini v1 board that was defective. The chip shortage is affecting electronics quite negatively, and QC has taken a turn for the worse. It’s entirely possible that the GPS/compass module is defective. I’ve never had any trouble with ArduPilot’s detection of supported I2C compass devices.
You were right, I have a defective M8Q-5883. A replacement M8Q-5883 showed up in the Mission Planner Compass List without anything more than the default parameters.
I thought we had it but problems continued. Matek response was just as great as you Arducopter guys. After several diagnostic and trouble shooting steps they asked for pictures. Ughhhhh, my I2C wires between the M8Q-5883 and the fight controller were too long. Shortened the I2C wires to the length that came with the the M8Q-5883 and all of the issues were resolved.