I think these values are intended to measure relative complexity of different parts of applications and get insights into the GPU operations while performance tuning. So how about add description to reminder users like this:
Note: These values are intended to measure relative statistics generated by operations of the device. Be careful to use these values in the release version of applications, because various device architectures may count these values differently.

Originally posted by @haoxli in #794 (comment)

Hypothetically, if we were to create a class of API features that are only for development (have to be enabled by the end user, e.g. through a dev-tools UI), what could we put in that class? I think we should seriously consider having such a class, so we can provide useful tools without creating portability and fingerprinting hazards.

• Pipeline statistics queries
• Higher precision timers (if we lower the precision of timers)
• Source-mapped shader error locations (file/line/column) (probably unnecessary, apps can do userspace source mapping)
• Synchronously-thrown validation errors
• Possibly additional error information, e.g. more detailed/fingerprintable error messages
• Other fingerprintable things?
• ?