I think the task name is also something like the unique identifier of the schedule: Evey “action” cfschedule does is done by using that name as the unique selector. You’d need to create some kind of function that does an exact copy of the task with the new name and delete the old one in the admin. But before doing it, you must also check whether a task with the same task name doesn’t exist, otherwise it would overwrite it. If not available, that would be an enhancement of the admin.
However, for every new cfml app I create, I would not use the admin for setting schedules anymore. I’d use a component that onApplicationStart checks for schedules on the flyby using the cfschedule task, and create the schedule programatically if these aren’t present. That makes everything more portable and “backup-able”. You also wouldn’t loose any schedule setting if the context gets wiped out because of updates.