Recommendations on creating user-objects on system database
I can think of a few questions about this implementation that I would want to know before continuing:


What happens if, somehow, microsoft creates an object with the exact same name in a new version?
If databases are migrated to a new server, how will anyone know that there's something in master to migrate?
What happens if your objects corrupt the master database?
What adverse affects would having extra data in master have on the instance?
What would happen if an in-place upgrade was performed on this instance? (ie, upgrading 2008 to 2008 R2)
How would restoring the entire instance from backups be affected?


Most of these I don't know the answer to, but they're questions that come up when I contemplate putting objects in master.