Choria does do some caching etc but will try to get every file from the module on all hosts before trying to run any task to ensure consistency
Every file is cached individually so same file across multiple modules won't be stored many times - of course people do clear the cache though
But the client fetches all the file meta etc and then sends that to the nodes so they can verify - not all nodes need access to the tasks api for that kind of thing and anyway the goal is to ensure all is the same so it's fetched by the client and sent
With tasks with many files that metadata becomes huge and bumps into limits