While it is possible to handle this using extend-immutable-calls, you'd have to manually add all NewType wrappers into the list if the NewType is using an immutable underlying type. The user experience would be much simpler and nicer to just use the underlying type of the NewType.

Of course, this would require some amount of type level knowledge and cross-file knowledge so I know that it'd be hard for ruff, but it also certainly doesn't fit in a type checker.