When getting the Embeddable Fields, the module just does a check on the entity type, not considering that could be bundles that are marked as not to be translated, this made the final file getting embedded entities that should not be translated.
Create two paragraph types one translatable and one that isn't. Create two fields referencing this paragraphs. Generate a new job. The exported file gets both field with the referenced entities.
Active
1.14
Core
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
We are also facing the same issue in the project. I tried #2 patch and it is working fine for 1-to-1 mapping. Eg, Content type field is referenced with one paragraph type then it is working fine.
But let's say the Content-type field is referenced to paragraph type A.
Now Paragraph type A also has a referenced field that has multiple paragraph types B, C, and D.
Paragraph types C and D are not translatable still it will be part of the translation file.