Client rendering intents vs. compositor color effects

Somewhat related to swick/wayland-protocols!31 (warn the end user if color presentation is compromised), what should be the priority between client set rendering intents and arbitrary color effects in the compositor?

Compositor color effects are color adjustments that are not necessarily called for by rendering intents, like blue light reduction, saturation control and vibrance control for example. They are still end user controlled and therefore the end user wants them when they happen.

Should colorimetric rendering intents always disable all compositor color effects?

Are compositor color effects always just fine with perceptual and saturation rendering intents?

Presumably applications would use perceptual rendering intent unless they actually have a good reason to use something else. That good reason is likely end user expectations. So we kind of can have the end user disagreeing with themselves.

Who should win?