Your description of needing to open another screen to remember what scene/activity a button number represents, that was exactly what I had in mind when I made my original request.
I also understand what you mean when you talk about not using the double-tap and hold options for a virtual button, another button number makes perfect sense.
With both of those points in mind, the reason I was entertaining the impacts for physical buttons with @calinatl was that I would expect any change like we are suggesting would be a change available for any button not just virtual one's. When you are presented the option to select a button device in an automation, it is looking for devices that implement the appropriate button capabilities, regardless of the driver involved. The naming of the buttons could, I expect, be made to be an optional configuration that could default to the current button 1, 2, etc. The point being, I do not expect changes to Apps like RM and Button Controller are likely to include code that behaves differently depending on the driver used for the button device, rather, allow any button device to record button names as an optional setup... If we get our request 
