Filtering out Flir VUE Pro from being recognized as an additional Controller

When a flir Vue Pro is connected via serial for Geotag (atleast on there latest firmware) you need to have both TX&Rx connected in order to tag photos. When connecting your pixhawk to Mission Planner you will see the Com port of your Vehicles and below with the same Com number a Camera as also seen on the ardupilot wiki (https://ardupilot.org/copter/docs/common-flir-vue-pro.html)
Problem with this is that it creates on mavproxy a mode indicated as 0x00000040
After my discussion with @peterbarker on https://discuss.ardupilot.org/t/0x00000040-spamming-mavlink-and-seen-on-mavproxy/61211 and testing all things i could think plus following his suggestion i am unable to make it go away.
I am almost sure its 99% Flir/Ardupilot Firmware related and i wanted to know if there is a way to filter it our of mavproxy.

Start by reproducing the serial-connected FLIR Vue Pro and Pixhawk setup described in the issue, then trace where MAVProxy recognizes the 0x00000040 mode. Done means this camera connection no longer creates the additional Controller mode while normal controller recognition still works.

Written by the indexing model from the issue text.