There would unlikely be any straight forward approach, as there is no out of the box functionalities to handle the senario.
While I understood this is common senario in real world use, I believe every customers are doing what they think things best workable for their implementation.
For example, net_connect probe, its monitoring policy is found in cfg file only.
Technically speaking, probe with the same cfg file content at any robot behaves the same.
Therefore, just copying the file is adequate.
However, take a look at the other probe, snmpcollector, monitoring policy is spread out in the multiple locations (cfg, internal database, template files, vendor cert bundles, etc) so different approach is required.