On mid-term a step closer to SimRel
I suggest you do it the other way round (which is also the traditional way of doing things): first get into SimRel, and then consider joining an EPP package or creating one.
In short term a simplified maintenance, since it will be easier for the EPP maintainers to update all those ids and urls with a search all, including .embedcdt at no extra cost, instead of me continuously figuring out what changed in .cpp and manually update .embedcdt in my fork, with each EPP run (M1, M2, ...).
IMO, the strong coupling with CDT package seems to be yet another hint that inclusion in the CPP package seems to be a better solution ;)
And FWIW, if you want an EPP package, you need to be ready to contribute to the maintenance anyway. Although some tasks are "bulk" changes applied to all packages, the package maintainer is still responsible for maintenance and tests of its package and mustn't rely on the idea that 3rd party folks take care of everything.
