Observed in the field (2.0.1) and reproduced locally (2.0.1) and on Linux CI (2.1.0).
1) Edit any Template to change any field that is displayed in the Load Template dialog's grid view (activeness, privateness, name, advisor)
2) Click "Load Template" again
3) Row representing the edited template will not reflect changes. (Or, if authorship changed, the row representing the new Template will not be present.)
The database will have been updated correctly, though.
Affects all creation scenarios, not just the clone-on-authorship-change case.
Basically, just seems that the dialog caches its contents until you navigate away from the tool and come back. Data isn't actually being corrupted nor incorrectly stored, but it's very disconcerting to an end user because it looks like the changes didn't take, especially for the fields we don't display elsewhere (activeness, privateness, adivsor).