I would definitely support a revisit of SE-0132 in addition to several other API rename suggestions.
It was already being possibly considered in response to SE-0279