Limit ability to copy between Projects (between different sibling EPS / OBS nodes)

Hello,

I am trying to figure out a way to limit the amount of extraneous global and project data that may accumulate in our EPPM database over time.

The core issue is that when new projects are created, schedulers will take the path of least resistance by copying old version of a schedule from another project and use that as a starting point for new projects.  Unfortunately, that schedule from another project also carries over a lot of irrelevant calendars, labor and material resources, user defined fields, etc  (which is what I call "schedule support data").  Over time, this causes schedule bloat, which in turn causes usability and performance issues.