This is the preservation component of the formal concept "type safety". Thus any type safe language must achieve this.
> Objects containing the same values should be equal by default.
This one really depends on a lot of things. You may have abstract types in which case equality should not be implicitly defined. You may also have codata types where you cannot merely compare "value containment" since it's no longer a concept. These are both important things which are sometimes called "objects" and shouldn't be eliminated from languages.
Really, this is a lot more complex than it seems. But at first swing: "structural equality should be everywhere and reference equality isn't a genuine concept" is pretty great.
> Comparing objects of different types is a compile-time error.
This is a-OK so long as it's easy to prove when two dissimilar types are actually the same. In cases where that's not true there are other forms of equality which are useful.
> Once created, objects and collections must be immutable.
This is a little overly strong. Regionalized mutability can be made to be referentially transparent from the outside.
---
But man, yeah, this are tiny nits. This list is great.