Makes sense. Bdf is an X11 format, and X is deprecated technology. X font rendering is certainly deprecated.
Xorg isn't going anywhere for a very long time.
Matter of fact, rendering everything is moving to client side, hence why X is increasingly unnecessary, and why Wayland is designed the way it is.
Oh, and among "Wayland fans" you can count just about everyone who knows anything about the Linux graphics stack, except maybe for Keith Packard. So yes, getting traction is important, because no one wants to keep maintaining the broken X architecture. Xorg is largely maintained by Red Hat who have put it in "hard maintenance" mode with virtually no new development.
I prefer stability.
Meanwhile, Wayland has pretty much the same graphics server architecture that Windows and macOS had decades ago. It finally brings the Linux desktop architecture in line with the state of the art. There may be a rough transition period, but the faster the Linux community pulls together and rips the X band-aid off, the shorter that period will be.
This sort of "lets rewrite, and rewrite, and rewrite, ad infinitum" stuff is a major problem with the open source community. It leads to an enormous amount of wasted effort in an area where effort is always needed to address real problems around usability and hardware compatibility.
The usability improvements on the Linux desktop happened in spite of X11. The conversation is about font rendering—and why should font rendering be a part of your windowing system? For most apps, it’s not—it’s in Pango, and Pango dropped support for X fonts. All of these changes which already happened have been eroding whatever advantages X11 offered in the first place.
So it’s time to decentralize all the random functionality in X11, and just move it into client-side libraries.
The other problem is priorities. There are a million other much higher priority things: better hardware support, better support for laptop power management, endless usability improvements to desktop apps, etc.