I don't think it's necessary... this check is for non-compliant geojson, whereas the support that's being added is for well-vetted objects. I maintain the legacy check for compatibility but do not complicate the logic going forward just for invalid data.