Through further digging, it still gets detected as a mouse, however, I was able to bypass it using:
Section "InputClass"
Identifier "Saitek Radio Panel"
MatchProduct "Logitech Logitech Flight Radio Panel"
Option "ButtonMapping" "0 0 0 0 0 0 0 0"
EndSection
I had been trying several variations and the above still has one button act like a scroll wheel tick upwards, but only outside in a browser. It wasn’t till I dug more into the definitions in the hwdb that I realized that the names and info from lsusb was different and that getting the name and info from /proc/bus/input/devices would allow that to match and work.