Its still the same extension, same source code, same logic, just less capable

the same… but not the same… ??

I think the technologies are quite different.

uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU/memory resources while content blocking is ongoing -- uBOL's service worker process is required only when you interact with the popup panel or the option pages.

Are you claiming non-lite does the same, plus more?

You say it's the same source code, but it's a different source code repository. non-lite, lite.