So I guess this could be phrased as: are there functions that return null, for whom the meaning of null is significantly different from raising an error...
...and the answer to that is yes. For instance, TRANSCODE/NEXT will return a null when it has reached the end of the input and has no value to synthesize. But it raises a definitional error if there's a syntax error.
Pretty clearly we don't want a casual MAYBE to conflate those. So I guess it's a MAYBE TRY if that's what you mean. 
But for whatever it's worth, this really doesn't seem to come up that much. At least not in the code I have. Picking out of range on purpose is rare. And even rarer to try to pipe that to a void. There was only one instance (I thought there'd be more). So I don't think it's that big a deal.