To help clarify, I use my personal Lancache as a means of storing my games when I need to free space on my computer, by storing them on a NAS. This has benefits over using backups, like Steam's natives, because of multiple reasons:
The process of backing up takes time to compress, possibly even storing in multiple blocks.
The game that gets backed up could get an update, resulting in said backup being out of date.
In order to get the updates, I'd have to reinstall said backup, then download the update, and then save it again.
Reinstalling the backup takes space and possibly lots of time as it's decompressing large blocks.
Using Lancache, I get around this by having it automatically stored in the raw CDN setup, ie encrypted and compressed manifest and depot chunks. It's basically pre-backed up. If I uninstall the game from my PC, I don't need to run a backup process before uninstalling it, saving me time, and if I need to reinstall, I don't have to wait for Steam to grab each block I created and extract the data. Only down side is that in order to install updates, I'd have to reinstall the game to my PC, which will grab the cached 1MB chunks from the Lancache server, and cause it to grab any chunks from the update that I don't have.
If this software could use Lancache, which steam has natively supported for some time, it just needs to detect that Lancache is running on the local network, then what it could do is use that to grab the chunks from any of the Steam CDN servers, not having to figure out which ones have the game depot, and have it store them to the lancache drive. If it doesn't actually save the chunks that it gets cached, then I wouldn't have to worry about needing free space for them, but it would also provide the benefit of allowing one to regularly run to any cached apps and games that received an update since the last time files were downloaded.
I brought up No-Into earlier, but that'll be for another post/thread.