I'm not sure I've stated my case well. This isn't a database determining it's backup schedule (or maintenance or anything). This isn't a developer doing it. This is still the DBA. This is still the SQL Agent and instance level work being performed. This is, however, the DBA or someone with knowledge, choosing the backup/maintenance/etc. schedule and STORING it in the database. If the database moves to another instance, the backup schedule gets populated into the instance level jobs.

This is really about keeping metadata about backup schedules, maintenance, needs and requirements, in the database. The "who" decides it is no different than today.