By the same reasoning, we should remove printf from libc. It's a terrible, awful, crufty API with threading issues, and it's overhead on modern windowed systems is just horrible.
If we released some sort of libc for embedded systems, specifying only fprintf(), your analogy would be valid.
a conforming freestanding implementation is only required
to provide certain library facilities: those in <float.h>,
<limits.h>, <stdarg.h>, and <stddef.h>; since AMD1, also
those in <iso646.h>; since C99, also those in <stdbool.h>
and <stdint.h>; and since C11, also those in <stdalign.h>
and <stdnoreturn.h>
So yes, a conforming (freestanding) C implementation without printf for embedded systems can exist.