Why doesn't CREATE2 hash endowment?

questions
opcodes

#1

CREATE2 is useful for state channels so a user is certain that at some point a specific contract can exist at an address which can be calculated beforehand. That this address is created from hashing the current address calling CREATE2, a salt and the deploy bytecode seems logical to me. However, in a constructor (and even when calling the CREATE2 opcode) we can send value together with the deployment bytecode. What was the design choice not to hash the call value?