So I recommend you to look at whatever platform that will work locally only or at most, peer-to-peer. That way, you can always compress / decompress before letting the data out to whatever will use it.
In a client - server mode, that means you are server side because the server must be able to do its own job and you can not guarantee that all clients will be able to do what is required. You can also see the server as a client of its own service, like the mail app I told you about.
Second thing is to avoid whatever is mixed with encryption. As explained, encryption and compression are no friends.
There are 3 states in which data can exist : Online, in transit and Offline. Data is Online when it is in a single system. It is in transit when moving between multiple systems (network). It is offline when not in any system (tape backups, …).
When adding these facts, that basically drops anything network or protocol related. Today, basically all protocols and communications must be encrypted.
That leaves you with 2 states : Offline and Online. What you described as the benefit from your algorithm makes it pointless for Offline storage. The data itself being 100% static and at rest, no need for a compression algorithm that offers live modification.
So you are down to local online storage, preferably without involving encryption. You can compress before encryption. There are ways to do it properly. Just learn a lot about the subject before you try to do it. As an example of such a use case, you can look at Veracrypt.
If you will rather avoid encryption, then look at filesystems, e-mail storage like mbox format or log management.
Log management is probably your best bet : They are huge, they compress perfectly because they are text only, no encryption, they are local in the system, …
Maybe trying to tie yourself in Elastic Search or Graylog ? Syslog-NG or a new home-made log manager ?
Good luck finding a business case for your creation,