My understanding is that the Go standard library prefers that the entire underlying logic of ECC should be hidden from the user, like in "crypto/ed25519".
However, they can't get rid of elliptic.CryptoParams due to compatibility. It's not a good idea in a general sense to use CryptoParams because it uses big.Int which is not side-channel resistant. For these reasons I don't think it's likely they'all add point inversion.
If you do want to go on... you can "invert" a point ("negate" would be a better term...) by simply setting y = n - y, for example:
y := new(big.Int).Sub(curveParams.Params().N, y)
Best regards,
Conrado