Is there a way to swap unevaluatedProperties to additionalProperties?

[Devon-White]

I'm familiar with the reason TypeSpec decided to use unevaluatedProperties instead of additionalProperties, which is outlined here: #3549

However, I wonder if there are cases where a model is inheriting another model's properties inline via is where unevaluatedProperties actively hurts the error messaging and IDE validation experience.

Refer to the two pictures below. One schema uses additionalProperties everywhere while the other uses unevaluatedProperties.

Context: The model requires a function property to be set. The pictures below show the difference in error messaging when using tools like Monaco editor (VS Code) and CodeMirror:

unevaluatedProperties

additionalProperties

It would be nice to have the ability within TypeSpec to control this. Is there any solution today to handle this?