I’d like to see some discussion around a migration plan, before even discussing what token is the right token (as I keep highlighting). If an approach is taken that means the existing subsidy is stopped and pointed to another token, this has a lot of implications to the end users who are invested already. They will need to be made aware of this change and given the tools to withdraw from one and migrate to another. This will require development effort on the side of wallets + dApps + indexers, who have integrated this feature. These teams need to be involved in these discussions.
To do this correctly, would mean that users would need to see some kind of a banner or notification of these changes inside these apps, with an explanation and possibly links to further info, as well as the functionality to migrate. There is a lot of work here.
Someone is also going to have to produce an article (way in advance of the actual change) that will answer users questions. A new standard for the network constants will most likely need to be agreed, if this is likely to change multiple times, developers would need an easier way to manage this, rather than pushing manual updates to point to a new token. App developers will also need time to do all this, and make sure they can get updates into the app stores in time.
Launching such a change without users being notified (twitter is not sufficient), understanding what it means, or anyway to act on it inside their apps, would be a PR disaster for Tezos that should be avoided at all costs