Welcome to 2018

Sorry to be 'well actually' cat, but ... Wayland itself is just a protocol and a library to (de)marshal requests and events. Its deployed servers are GNOME Shell / Mutter (an implementation of a server) shipped in Fedora and others, KWin, Enlightenment (shipped in Tizen), and others based on Weston, wlc, et al.

In a Wayland environment, apps based on toolkits like GTK+2, old Qt/EFL, or any of the long tail, do still talk to a very real X server in Xwayland which forwards window content and input events back and forth between the Wayland server and X11 client. Notable holdouts include Chromium (and anything based on Electron), Firefox, Steam, Inkscape and GIMP; most of these are works in progress and have experimental native builds.

But anything based on GTK+3 or newer, or current versions of Qt/EFL, will be a native Wayland client with no X proxy in sight unless explicitly requested. If you take the Fedora 27 default GNOME session, many of the primary applications such as Web, LibreOffice, Videos, Evolution, Files, GEdit, et al, are all native Wayland clients.