So, because of the way I2C works, everything on bus 4 is going to also appear to be on any of the busses downstream of the switch. So, your output is identical to mine (except my own device appears, as expected, on bus 8, on my board). My strong suspicion is that your device is in some way not working and that the mangOH is fine. i2cdetect is showing you that there’s a Linux driver loaded for the I2C switch (at address 0x71 on bus 4 and all other buses) and i2cdetect is fundamentally working. There’s not a lot that could be wrong with those symptoms other than your device having some connectivity issue.
I suppose it’s possible that the two zero-ohm resistors (R365 and 366) are somehow missing on your board but they certainly weren’t on mine (I ordered mine from Digikey).
To check the board, check to make sure the two I2C pins on the Raspberry Pi connector are both pulled to 3.3 volts. If they are, then the problem is almost certainly after that point. If they aren’t then there’s likely a physical problem with your board.
As for your second screen grab (i2cdetect using “write” mode), that does not work on this master interface. Not sure why, but read mode works fine.
For comparison’s sake, here’s my software versions:
Firmware Version: SWI9X06Y_02.14.04.00 a03347 jenkins 2018/02/19 06:13:56
Bootloader Version: SWI9X06Y_02.14.04.00 a03347 jenkins 2018/02/19 06:13:56
MCU Version: 002.007
PRI Part Number (PN): 9907365
PRI Revision: 001.004
Carrier PRI Name: GENERIC
Carrier PRI Revision: 001.012_000
Last Reset Cause: Power Down
Resets Count: Expected: 52 Unexpected: 39