[css-color-hdr] Requesting Absolute HDR Mode and listed differences from Adaptive HDR Mode

I (and others) have the need for the following full hardware stack viewing modes (especially Absolute HDR):

Absolute HDR:

Browser Requires User Permission (Like asking for your location, this will let the website exactly fingerprint you.) (User still has full control to keep any Filter, or for "Passthrough Mode" if they desire accuracy)
Calibrated Fullstack (The manufacture+user Calibrates their display TO ABSOLUTE, if they desire accuracy) (Monitors age and have settings, the user Recalibrates over time and after changing settings, if they desire accuracy) (Calibration is Fullstack and will try and undo all meddling/mapping by Display, OS, and Filters; if the user desires accuracy)
Get Light/Dark Theme (I need to know if it is Light or Dark Theme and when it changes)
Get Ambient Light Sensor (I will present my own brightness settings and do my own adjustments, per each app's needs) (Backwards compatible by having a settings panel ask the user to select paper-white)
Clip and Get Clip Limits (I may adapt to stay within limits of display like primaries' cie colors, min, max, and only X% of screen can be over Y nits) (Adjusted to current Calibrated limits, not manufacture marking material, when possible)
Set Absolute PQ/F16 (I indent to render this exact nit + cie color, I desire accuracy)
Usecases: Better Framerate, Better Battery Life, Calibration itself, Research, Exact Reproduction, Mastering Env, Showcase Capabilities, Compare Hardware

Adaptive HDR:

No Permissions Needed
Get Light/Dark Theme (I need to know if it is Light or Dark Theme and when it changes)
Set Mastering Limits Per Frame (I need to have this amount of PQ/F16 Brightness Headroom, even if I am not using it this frame) (I need to display X% of screen at over Y PQ/F16, reduce Global Brightness as needed for hardware limits) (I need details at this dimness to be visible, Increase Mapped Floor Brightness as needed)
Set Adaptive PQ/F16 (This is the color we picked using and within our Mastering Limits)
Auto Color Filters (Color vision deficiency, Primary Color Adaption, Time of day, Blue light reduction)
Auto Mapped to Ambient Light Sensor (For Paper-White, I do NOT get read access to Sensor Readings)
Auto Mapped to within Clip Limits (I do NOT get read access to the Clip Limits)
Usecases: Accessibility, Effortless, Broadcasting, Replay in different Env, Managed Color

Performance HDR:

No Permissions nor Sensors nor Mastering Limits (User manually adjusts Brightness when needed)
Easily Disable Individual Filters and Mappings (Disable Anti-Clipping Mapping)
Get Light/Dark Theme (I need to know if it is Light or Dark Theme and when it changes)
Set faster of PQ/F16
Usecases: Better Framerate, Better Battery Life

I believe that Absolute HDR is not receiving enough attention and requires the most coordination between the Monitor, Graphics Card, OS/Desktop, Browser, and Calibration Software.

I've been thinking about absolute luminance rendering intent for the Wayland window system protocol. I'm fairly confident that from the Wayland side the "calibrated full stack" and "clip limits" will be available in some form.

I'm not sure the choice between Adaptive HDR and Performance HDR belongs to applications, though. This is more an end user policy, e.g. Adaptive on AC and Performance on battery, or different on different displays due to being connected to different GPUs like iGPU vs. dGPU.

"No mastering limits" is also problematic from a window system perspective, because end users would need to adjust things manually for each window, or even for each web element. It just means the end user is asked for a substitute of the mastering limits, which I believe should only be the last resort after defaulting to some mastering limits doesn't work well enough.

w3c / csswg-drafts