Right. Wayland is basically just a buffer-swapping and event-handling API.
What it does, though is offload a bunch of the stuff that X used to do into the compositor. So Weston (and Kwin/etc.) have to do things like handling the mode setting.
Weston does that by using KMS, though the proprietary drivers are free to modify the code as necessary to work with their drivers.