URGENT - Draft Content being sent in Email Delivery when using Content Fragments - ACC + AEM Author integration

We are using Enterprise level shared Content Fragments that are authored and managed by a different team on our Email containers.
Currently we have Adobe Campaign Classic integration with AEM Author, as we are using shared Content Fragments there is a high possibility that the Email's being sent out (especially always-on containers) have un-approved (modified after published) CF content.

To mitigate this risk we are doing a POC to connect ACC to AEM Publisher but we noticed that ACC writes back a cq:acUUID to AEM publisher and upon republish of a container after any modification the property on publisher is wiped-off which is resulting in "No Newsletter Found with UUID" error in ACC (as expected since it is not on author).

As an alternative solution we wanted to keep the ACC integration with AEM Author but intercept ACC requests using a Sling Filter for request URL's ending with "campaign.content.json" and fetch content from publisher but we found that whenever an email container is accessed with "campaign.content.json" the page and it's referenced assets are re-published too OOTB.

Now it is concerning that AEM re-publishes Draft content and send's email delivery and we are out of options for safely using shared Content Fragments on email containers without the risk of sending emails with work-in-progress (Draft) content.

It would be great, if you could provide a way to either connect ACC to AEM Publisher or stop re-publishing when campaign.content.json is being requested.

Start with the AEM Author/ACC integration behavior described for campaign.content.json, including the cq:acUUID write-back and republish sequence. Reproduce the request against a modified email container and compare Author/Publisher behavior; done means either ACC can safely use Publisher or requesting campaign.content.json no longer republishes referenced draft content.

Written by the indexing model from the issue text.