There is no need to remove the F-key menu system to implement this additional interface and if BIS decides to replace that with a more intuitive keyboard/mouse operated system (like a commo rose) sometime, that is a completely separate issue from the UDP interface. Ideally the list of commands recognised on the UDP interface should be kept in sync with any other command interface systems but one of the advantages of the system X-plane uses is that it is possible to add new commands whilst keeping the existing ones for redundancy/backwards compatibility. So if someone realises there was a spelling mistake in one of the commands, or that it can be more accurately named, the new command and the old command can co-exist, to avoid the need for users to edit their existing profiles, whilst only the new command can appear in the F-keys or commo rose menus.
This interface can not only be used for AI commands but also for interfacing physical buttons and switches to commands, such as Detonate, Gear Up/Down, etc. These commands can be sent from voice recognition programs but also from touchscreen programs and utilities that interface between games and Arduino boards with physical controls attached. If the control panel is built specifically for A3, then the Arduino firmware can send the required commands over UDP directly, with no need for a utility in the middle and it can be used as a two-way interface if desired, so data can be sent from A3 regarding gear or flaps status, how many seats in the current vehicle are occupied, etc and be indicated by LEDs or other displays connected to the Arduino.
So whilst a simpler and more natural way of using voice recognition to control the AI is my main motivation, implementing the UDP interface provides for a lot of other possibilites. I would think the work required would be fairly minimal, as pressing an F-key sequence obviously results in the appropriate piece of code being triggered for that command, so all that's required is the UDP interface itself, which waits to receive one of the commands and each of those commands is associated with the appropriate piece of code to trigger. This may even be something that could be implemented as a mod but it would probably need BIS to provide a way to hook a UDP interface into the code first.