Haitzler has uploaded his 79-page slide deck for those not in Brussels for FOSDEM 2016. This Enlightenment/Tizen presentation is all about their Wayland usage and implementation.
Among the reasons expressed for "Why does Tizen REALLY want Wayland" are better security and client isolation (X11 can't be trusted!), better zero-copy rendering support, ensure perfect rendering with no partial screen updates, massively reduced round-trips for input and rendering, far better support for hardware layers, and proper rotation handling.
The slide deck does a nice job in comparing the differences in approaches between X11 and Wayland, so check it out if you are still unconvinced about Wayland being superior to X11/X.Org. Much of Enlightenment is already ported to Wayland from the client to compositor work as well as making use of libinput. Enlightenment now acts as both a Wayland compositor communicating directly with KMS while still having its X11 window manager and compositor functionality. Enlightenment EFL using applications still have both X11 and Wayland support. Tizen continues working on moving to Wayland and ensuring all needs are met.