You have options--none of which use the actual "button text" that's part of the button setup. You leave the button unlabeled but then place either a merge variable or a field on top of the button. If you use a field, you can either, use a merge field, a regular field with access behavior blocked or you can group the field with the button's graphic option before you set it up as a button.
With all of these, you then use the button's script to alter the value of the field or variable to change it's name and you may need a script trigger to perform a script that sets the button's original label if you use a variable or a field with global storage.
Thanks very much, Phil.
These options sound totally workable.
Appreciate the time you took to leave such a great reply. :)