As article is detailed it shouldn't affect the Big-IQ or BIg-IP still better test with an F5 virtual machine trial license on-prem in VMWARE or AWS and play first with it.
The F5 BIG-IQ proxy is just to proxy the f5 BIG-IP REST API commands as you add the device id in the URL path when pushing REST API commands.
https://www.f5.com/trials
https://aws.amazon.com/marketplace/pp/prodview-wjf44onau666e
The ADC Discover Config Task seems to me normal to run when using the BIG-IQ to control the F5 devices as someone may have modified the nodes directly from the F5 BIG-IP GUI, so better to discover the config again just in case.
Another option is for the server/web admins to dissable the nodes with a special response health monitor string:
https://support.f5.com/csp/article/K12818