I repeat again the first link provided before: https://gist.github.com/probonopd/9feb7 … 9f2d1f2277
That's enough in the current point to conclude besides we have also to make the system running. So wayland is not an option at this point. HyperbolaBSD is right now even an independent system, not just using OpenBSD upstream. It is a hard-fork for the kernel, so this means it stands on its own base. It is a new BSD descendant operating-system!
And many window-managers are right now not working with wayland, being left in the need to add even more functionality just to stay compatible and working. We want to provide a stable, working system. I know the lines some people quote about wayland being "not that bloated". They misuse the definition of "bloatware" itself, out of the reasoning it works in some way for them. Yes, if they don't care about packages and the dependency-tree outgrowing? Their decision. But ours is another one. And if there is interest to test with wayland when HyperbolaBSD is available, feel free for everyone doing that. We have other and better things to do, keeping the system running and packages working. 
Others do what others do, Hyperbola is independent and there is no need we jump ahead for others doing. And I repeat again: Whenever "wayland" may (or may not) getting better useful with most of the points named under the link provided solved, we can take a look on. Until that day Hyperbola does what we think is best for the system: First getting HyperbolaBSD to be stable and running fine. Then packaging what we provide already and after that provide a stable system-base. What people create out of this, is up on the individual decision to make at that unnamed point in the future. And until now Xorg-compatible server is fully sufficient as we have it today. Please keep in mind that we also need to look over possible blobs elsewhere with every new release published. So if you are interested to support in development there, feel free doing so. And to repeat: HyperbolaBSD is not OpenBSD, so we do not run behind the OpenBSD-development. We stay independent and this is an own BSD descendant operating-system.
And to quote from https://blog.netbsd.org/tnf/entry/wayla … rials_and:
[...]
The Wayland "reference implementation" is a small set of libraries that can be used to build a compositor or a client application. These libraries currently have hard dependencies on Linux kernel APIs like epoll. In pkgsrc we've patched the libraries to add kqueue(2) support, but the patches haven't been accepted upstream. Wayland is written with the assumption of Linux to the extent that every client application tends to #include <linux/input.h> because Wayland's designers didn't see the need to define a OS-neutral way to get mouse button IDs.
[...]
[...]
In general, Wayland is moving away from the modularity, portability, and standardization of the X server.
[...]
Summarize in the end: Yes, wayland may or may not run on *BSD, FreeBSD has included it. But as mentioned: HyperbolaBSD is independent and our main focus is stability instead of the "hottest new development" to be included. This does not underline any reject, but the last time to repeat to take a look on own favors if something is wanted.
Human being in favor with clear principles and so also for freedom in soft- and hardware!
Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!