Ironically, CRLite seems similar to the approach Apple was (is?) forcing for "content blocker" extensions to Safari--pre-supplying a canned declarative blacklist to Safari, instead of Safari allowing extensions algorithmic access to the current URL.* Their motivation was supposedly to increase user privacy. Funny how they didn't think of that in the CRL and app-blacklist cases. Perhaps they were worried the locally-cached lists themselves would be subject to attack?
*In my opinion, in the content-blocker instance the result is a much poorer user experience (ad-blocking effectiveness, flexibility) when compared with e.g. uBlock Origin, and one of the reasons I continue to use Firefox instead.