GNSS Dead Reckoning — Sensor Fusion Filter not necessary?

My question might be a bit off-topic but I don't know where else to ask.

When I do have a GNSS Module with integrated IMU and Dead Reckoning, for example, the Ublox ZED - F9K.

Does it still make sense to use a Filter for fusing GNSS and IMU / Odometry data or is that not necessary as the Module is handling that for me?

Or will the Dead Reckoning just enhance the precision after applying a Filter even more?

Question

Is it necessary to use any filter to fuse Ublox ZED-F9K's GNSS and IMU/Odometry data?

My answer is NO, for the following reasons:

(1) GNSS and IMU are independently developed modules with matured software. It is unlikely for the vendor to "fuse" them at the hardware level. A more efficient method is to let the MCU/SBC to talk to either or both guys using I2C, UART, or SPI.

(2) uBlox uCenter uses very simple, text based NMEA0183 protocol, and update rate is of the order of 25Hz, so the user can easily pass the slow GNSS data to IMU for processing.

Discussion, Conclusion, and Recommendation

I think it is not a good idea to use the expensive US\$300 ZED-F9K module to do any feasibility studies. I would suggest to use two separate modules (1) UART NEO-8M, (2) Any I2C IMU and use Rpi python to do any system integration test.

References