Hi Luis,
I will try and expand to your questions :)
Can you tell us more about the generators and compounds that cause this?
I use generators to produce individual animated graphic elements that are published as editable (colour, position, font, size etc.) in FCP, which collectively produce a tool box, from which I produce eLearning video content, as these also need to be localised in different languages further down the production.
I composite these in various combinations in order to achieve flexible motion graphics to illustrate the courses learning content and speed up the workflow.
Did you make this compound clip right there on the timeline (it looks like it, by the name of the compound clip)?
Did things show up correctly before compounding?
I arrange the layers of animation according to the VO and then compound them on the timeline, then I make these individual 'storylines' in order to cut, stretch and transition them using FCP motion transitions.
If you take this same compound and put it in a new project, does it also come out wrong, or only when compositing several layers as in your screenshot?
The bug remains even if copied into a new project... as well as when I delete all 'Generated Event Files'... the interesting part is, that if I halt the rendering on the timeline, the render displays correctly in the viewer, but as soon as it renders the frame is offset to the top right and the image is flipped (or mirrored).
My project is set to:

If you double-click the compound and open it in its own timeline, does it look ok?
Yes... if I copy the generator out of the compound-clip and paste is in the timeline in its place, the bug remains as soon as i make it a compound again.
This is only happening in a few instances, as this is my workflow throughout every project ( which can range from 4min to 14min long), so it appears to be quite random, but definitely associated with compound-clips... mostly when they have been cut within the storylines!
I will have to do a bunch more experiments in order to figure out exactly what exactly is producing this specific bug, but it is new since I updated!!!