The main limitation is getting approval first to do something like this. There are many UI mods already integrated directly into FAF, and we're running on a blacklist for some others.
I would have thought this is mostly a moderation decision rather than a development one if we were to opt for a whitelist as opposed to a blacklist type of solution.
As to actual measures to combat cheating, then sure. I would need to first understand how FAF is built and what functions are available. A common way around maphacks was to have invisible units that get revealed by the hack, and are conditions to triggering some other code. This could be used if FAF supports hidden states on units.
For auto-eco mods or auto-micro mods, then a simple input check would work. Then a line would needed to be decided on what is "humanly possible".
If these have to be implemented as an anti-hack mod then these can be integrated into FAF.
If we can get a clear statement on a model for this, then I would be happy to have a look and learn and contribute. Otherwise, I might end up doing a bunch of work for something that is never going to be implemented and that otherwise serves no functional purpose.