Ah, I understand now. This first section is mostly my analysis and opinion the subject, but you can scroll to the bottom if you are looking for alternative approaches that might work for you.
Button Capabilities: Sensor vs Command
It’s unfortunate that Hubitat moved away from the Button capability which was a sensor only capability and aligned very clearly with real world physical buttons.
The new PushableButton and other xxxButton capability variants would be reasonable to me if they were distinctly used for Virtual Buttons as it makes sense to include commands in that case.
But there was already a Momentary capability that supports the push() command and could have easily been extended to support passing a button number.
Personally, I find it odd that the base PushableButton capability, which is one of Hubitat’s few departures from the original SmartThings capability model, includes a push() command as when it’s used with drivers for a physical button device it doesn’t make sense as you can’t send push() to the physical button device.
Voting
That being said, I’m fine with leaving the feature request open. It hasn’t picked up many votes, so it won’t be prioritized at the moment, but sometimes these things pick up traction over time.
Dynamic Run Rule with Parameters
In the meantime, also keep in mind that you could create a single SharpTools Rule which sends the push() command to your button device and uses a Context Variable for which button to press.
You can then use any tile with a hyperlink action along with the special $.runRule() hyperlink syntax wherein you can easily adjust which button number is passed as a parameter:
Call REST API / JSON Directly
Alternatively, the thread that discusses the special $.runRule() syntax also mentions a special REST API Hyperlink syntax that you could use if you already have a Hubitat Rule setup or find the Hubitat Maker API more intuitive to use:
$.get("https://your.cool.url/?button=1")