I still think you are missing the idea here a little bit. I definitely understand the likelihood of you doing this is very slim to nonexistent, but I still feel the need to explain this for the sake of others.
AutoPkg only runs on a single system and generates the content. You could put it into the root server by hand, or have AutoPkg do it for you.
Once the automation is created and the content is being generated, it really only has to be done once and it could be done anywhere in the world by anyone as long as the results are then made available to you and you then put it into your root server.
There is no connection between the Mac running AutoPkg and the Windows devices you are managing at all. There doesn’t even need to be any connection between AutoPkg and the root server if you are willing to do the content import by hand. AutoPkg is just a way to automatically generate BigFix content. IBM uses other tools to generate the content that they publish in the patching sites. AutoPkg is a way for you to do something similar, but using a publically available tool.
Most of the content @hansen_m creates is automatically generated by AutoPkg, and there is a lot of it. Most of the content @strawgate creates is automatically generated by some custom PowerShell. A lot of the content I generate is automatically generated using Session Relevance and REST API calls, though I also use AutoPkg, and python scripts.
My point is that there are many different ways to go about automatically generating content, and AutoPkg is one you should definitely consider. Writing your own custom solution is another. You could also base it off of some of the published work by myself or @hansen_m or others.
This answer really applies to any question about IBM adding content to their patching sites. You or others could do it themselves using automation. This isn’t a small task, but I hope that a community could build up around doing this, with published scripts and tools for AutoPkg, Python, PowerShell, Session Relevance, etc…