It's just another variant of that: having INT32_MIN is just as bad: these things inevitably end up unrepresented in the typesystem, someone writes a naïve function over that, and suddenly your "nulls" are being summed or computed on, particularly when they're rare in the dataset, or at least in the one the coder tested with.
(Even in SQL, where it's a separate value — NULL — it's still an awfully weak type system, so sanity is by no means assured.)
Give me must-be-explicitly-handled Option<T>.
(So, I'd argue that even if there were a performance loss, in most cases, the gain in correctness is the right tradeoff.)