Differentiating between Machine translated ONLY and Reviewed translations

Problem Statement:
Would need a mechanism to differentiate and track content processed via machine translation (MT) versus human translation. The primary need is to automatically label and manage content that is machine-translated only (i.e., not reviewed by a human).
This labeling should update metadata and file attributes so that both internal teams and end users can easily identify the translation source for any given content.

Current Limitation
AEM Guides, via the AEM OOTB Translations project, does not provide an event or API to intercept the import of translation summary files.
As a result, there is no straightforward way to update labels or metadata during the import process.

Expectations:
Automated Categorization & Labeling (or Translation Status)
A clear mechanism to categorize and label MT-only content at the time of import.
Metadata should reflect the translation source (MT vs Human) in a way that is visible and actionable

In short:
When the Translation Status is “In sync” there is no way to know if it is a result of proper review or if it is “just” a machine translated result. This is specifically relevant in case of AEM Guides and large asset amounts