asMutable and asImmutablebehaviour aren't immediately obvious. How about cloneAsMutable and cloneAsImmutable?

clone also isn't obvious and is only there to retain API parity with the mutable version of clone.

The first point is more than just bikeshedding the wording if, say, cloneAsMutable works for mutable collections. This way, you can safely remove clone altogether.