There is absolutely no need to fiddle with anything to setup schedules, prune, and everything else.
Exactly. To use those scripts you have to understand how duplicacy works, what you want it to do, and then understand how scripts work, and whether they do wha you want. Too much extra work.
Judging by the link I assume you are using windows.
Your question boils down to two:
On the first point, it’s really, really simple. The beauty of CLI interface is that if you don’t know how to do something – the help is self discoverable.
For example, you don’t know what even to begin with? Run duplicacy.exe. It will print help, and list of commands. read them. You’ll realize “init” is the one you want first. But you still don’t know how to use it. Well, run duplicacy.exe init – you will get help on this specific command. Etc.
To summarize – you need to run init once, to initialize storage and repository. then you can run duplicacy backup, duplicacy prune…, duplicacy check, duplicacy restore, etc. as needed. Likely you want to use Tash Scheduler to schedule daily calls to duplicacy backup.
The important bit to understand is how duplicacy works. What it calls “repository” is a source directory you want to backup. you normally cd to that directory, and call duplicacy init. Then to backup – you cd to that directly again and call duplicacy backup. That’s pretty much it for the basic use. All data duplicacy needs to backup is stored in the .duplicacy folder right in the repository
Slightly more advanced – you don’t have to cd there all the time, and don’t have to store .duplicacy folder along with your data. How to initialize storage this way – see help for init command.
Lastly, a useful trick of you have to backup a few different folders that are not in the same folder hierarchy – you can create an empty folder, put symlinks to other folders you want to backup, and backup that folder. Duplicacy follows first level symlinks, so it will just work.
Yes, it will work just fine.
You can leverage duplicacy_web and steal the .duplicacy/preference files it creates and build on top of them, to avoid going through repository initialization, but you don’t have to, you can just initialize the same storage again (this time it will be recognized as already initialized and added instead) and backup will continue.
Ultimately, described what have you tried, and where did you get stuck – and we’ll try to guide you. Keep in mind, if it seems too complicated, probably you are not taking the most optimal path, there must be an easier way 
