I do not know whether this is out of scope but did anyone ever consider integrating with the paragraphs module?
At the moment I am building a replication workflow with nodes having paragraphs attached to them. For this cause I had to create a paragraphs storage class using ContentEntityStorageTrait and implementing a custom database update method to keep its parent's target_revision_id in sync with the paragraph's revision_id (else any change to the parent node entity through Entity API would trigger ContentEntityStorageTrait's save logic and create a new revision each time) which is naturally prone to error.
Also I had to replace the EntityReferenceRevisions field type class (which the paragraphs module uses) with my own implementation which has a similar functionality to multiversion's EntityReferenceItem class. I think creating a trait and using it in the EntityReferenceRevisions and EntityReferenceItem classes would be a great follow-up issue.