A custom solution would be required where the target system or Translation connector can read the node path details sent from AEM and obtain the dam:relativePath or cq:parentPath values from the jcr property using sling API or JCR API to display the full path at target system.
We recommend that you consult with your technical team to understand the feasibility of this solution approach based on your project or business requirements. They can provide further guidance on how this custom solution can be implemented and if there are any potential challenges or limitations.