Actually, to me it makes a lot of sense. We use variables, for example, for the company and product names and for the latest-release version, and on occasion we want to use these values also in page titles. One of the main advantages of using variables is that when a value changes you only need to make the update in one place. (There are also other advantages, such as ensuring consistency and avoiding spelling errors.)
Using archetypes or templates won’t help us because there’s no unified title format, it’s just that some titles might need to reference one or more variables. Also, archetypes are used to generate MD files, but once generated, if a variable value changes, we would need to manually change it in the relevant front-matter page titles.
Of course, often you can do a global search-and-replace, but not only is this less convenient and more error prone than just updating the variable value, sometimes the value is not sufficiently unique to support a simple search and replace.
It’s also worth noting that while some variable values are not likely to change frequently (although in our case, because the product is relatively new, the terminology is still changing), other variables are by nature expected to change — such as a variable for the latest product version number.
I believe it should be possible to implement a custom solution to this, but currently, in our specific case, it’s not something that we can prioritize.