By what you say, it sounds like a particular case of Hismo.
What Hismo does is to create a history model at entity level. So, you will have a ClassHistory with multiple ClassVersions corresponding to actual FAMIXClasses from different versions. Based on this information, you can aggregate historical properties based on version properties. But, you can also ask a ClassHistory if it is isRemoved or isLateBorn.
By manufacturing histories out of individual snapshots, you need a heuristic for identifying the identity of an entity. Right now, Hismo uses the mooseName for entities. Thus, moving a class between namespaces will not be captured in this way, but it can be identified after the main model has been built by applying heuristics that compare classes that died in one version with classes that appeared in the next version.