Does Tahoe-LAFS help with this project's intended use case, local encryption of files stored on various commercial cloud providers?

It looks like it is an off-label use, circa 2012: https://bitcartel.wordpress.com/2012/10/21/rbic-redundant-bu...

>Tahoe doesn’t directly support online storage providers as remote back-ends, but we can work around this problem by using sync folders, at the expense of local disk space

I noticed mention of a Windows virtual drive as a client; I believe CryFS requires "real" FUSE (aka not Windows).

DokanY (LGPL) provides a FUSE-compatible API on Windows.

Also, git-annex, although it's not a filesystem (IIRC there is some way to mount it with FUSE, but I don't think it's a good idea)

http://git-annex.branchable.com/special_remotes/

Interesting point mentioned about the Tahoe-LAFS remote there:

>Tahoe-LAFS does not support removing data once it is stored in the Tahoe grid