This change is a onetime activity for each node. Restarts won't affect this. That said, if you add a new node to the cluster or the Node ID changes for an existing node after restart, then you need to make this change for that specific Data-Agent-Queue instance.
We have taken three approaches to tailoring agent schedules in the field
a- a lot of typing to update data-agent-queue records (one per node)
b- overriding the ootb final rule-agent-queue records to create new defaults; blowing away all existing data-agent-queue records (activity or delete) and letting system generate new data-agent-queeu from our updated rule-agent-queue
c- writing an activity to copy or bulk update data-agent-queue