Woof-CE has four components, roughly.
1. The Puppy initrd.
2. The Puppy common scripts and app-lets (gtkdialog scripts etc).
3. The PET builder: a custom package builder that builds binaries from source.
4. The build system proper.
In my opinion, what makes Puppy a Puppy is (1) and (2) (but feel free to disagree with me).
(3) was once a separate script distinct from Woof-CE, but it was merged together to make sure Woof-CE didn't carry obsolete binaries.
(4) is the one that everyone complains about being complex. It's necessarily complex because it was designed to support multiple different upstreams and architecture (it can build from Debian, Ubuntu, Slackware, Arch, Void ... and for 32-bit Intel, 64-bit Intel, 32-bit ARM, etc).
If all you want is to build is 64-bit Intel Debian-based Puppy, the build system can be simplified tremendously.
and i am working on that now
Good luck.
Remember, though, the entire point of the exercise is to have a final system that will attract other developers to use it. Otherwise, it will be just "yet another build system".