This is just about reading GeoJSON, right? If so, then I think PARSE_DATELIKE_FIELDS (or DETECT_DATES) would make more sense to the user.

If I understand correctly, when writing to GeoJSON from other formats, any date types will always be written as strings, regardless of this option. The name "DATE_AS_STRING" makes it sound like the option controls how the output is written.