Hi Reddi,
I haven't implemented this exact scenario, but I came across the Route Email to Multiple Destinations capability, which looks very relevant to your requirement.
From the documentation, when this is enabled and an inbound email contains multiple recipients that belong to different destinations, Genesys Cloud creates a separate interaction for each recipient and routes each interaction to the corresponding queue or flow.
The resulting interactions still go through an Architect email flow, where Email.Message.route.id can be used to make the routing decision.
The only catch is that this capability is enabled at the organization level, rather than purely within Architect. I couldn't find an Architect-only equivalent in the documentation for splitting a single inbound email into multiple ACD interactions.
It may be worth reviewing this before going down the Loop + Agentless Email approach.
Full Genesys documentation:
https://help.genesys.cloud/articles/route-email-to-multiple-destinations/
Hope this helps!
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------