As rclone user I believe that the construct to use pseudo-remotes (I faced this with crypt some time ago) is complex for users. And the concept is being extended with cache / chunker / union?
and perhaps the zipper one ... (sending a folder with many many small files to a remote is a PiTA9).
The config file becomes clumsy and uneasy to understand.
As an example, read the following topic in the forum - Encrypted chunker
Perhaps time to rethink architecture/UX on this. I see two different building blocks but could be some more, and other alternatives.
a) using a kind of piping paradigm, user needs to specify end remote and the piping. the intermediate steps are transparent for configuration etc.
b) config file should pack around the end remote all needed information, not needing to have sparse pseudo-remotes detached from end remote configuration.
Piping should be logic. So, should we recommend encrypt then chunk and do not chunk then encrypt or otherwise?