The GhostBSD approach is simple. If you want a different desktop environment, install it from packages. If the community eventually produces a KDE Plasma or Sonic DE edition, you can install it from an ISO instead.
If you want something, build it. Waiting for someone else often means waiting a long time.
Building your own solution teaches you how the system works. You learn where the pieces fit together. You see what can be improved. Fresh eyes often find problems that everyone else has learned to ignore. When something breaks, you are in a better position to fix it because you understand how it was put together.
For a hobbyist, that's part of the fun.
My recommendation to the GhostBSD community is to automate customization with scripts. Install GhostBSD, then apply your own changes. Scripts are simple, repeatable, and easy to rerun after an update. If a system update changes something you depend on, run the scripts again and restore the system to the state you want. The same approach works if you prefer a custom GhostBSD kernel.
I've been doing this recently, and it has worked well.
