It may make more sense to expose a <port>:/metadata or <port>:/metrics/metadata (basically a different URL) on that same port that hosts the OpenMetrics output for these non-core metrics in terms of bucketing or classification, especially as type INFO, where the value doesn’t change during the lifetime of the pid.
The user can then hit one or two or both of these endpoints, if desired.