Hi Andrew,
Just a couple of observations from having been in the standards / W3C space for a while:
* I've never seen an argument for "this is needed for accessibility guidelines" work with HTML or CSS standards unless it also aligns with other priorities. (See also https://www.tpgi.com/html5-document-outline/)
* From the github issue, it took a lot of reading to work out the benefit of font-x-height, which is (I think) that you can set a font-size which would appear to be the same size across font-families.
* There is a mantra in the HTML/CSS space of "come to us with a use-case, not a solution". If you start naming things (like font-x-height) people focus on the wrong things.
* If there is a benefit to general web development (e.g. switching font-families doesn't cause layout issues), start with that, and then mention the accessibility benefits.
If you can edit your initial comment in the issue, I'd suggest putting the TL;DR bit at the top, but frame the name as "a CSS property such as font-x-height".
I've previously had a good experience with issues put to the CSS working group. They have a ton of issues, but they are efficient when they get to them. However, proposing a whole new property is a big deal.
I hope that helps,
-Alastair