Hum, the way I see it is your reply which is daft, nix is pointing out a particular use case (remote text rendering) where XRender may significantly outperform Wayland, and that this may become an issue, what's so daft about it?
As for me, I'll wait and see: on the paper XRender is much better for remote text rendering (an important use case), but X's implementation is so old and full of warts, that I think measurements are needed before implementing workaround on top of Wayland.