Doesn't particularly matter, but "read/modify/write" would be how you want it set initially
The number of data disks that are allowed to be spun down before turbo mode is invoked. IE: 0 means all disks have to be spun up for turbo mode to kick in. 1 means that all but one data disk is allowed to be spun up, etc
Nope. It just enables / disables the setting according to the parameters you set.
It overlaps. The command to turn on turbo runs every minute, and you've also set it to last for 60 minutes. There's 59 overlaps in every hour.
Sure. You can force turbo mode on (enabled) or off (disabled) at certain time periods. When the schedule expires, the setting in Disk Settings takes effect.
Depends. For small files, Windows (if you're measuring through it) may calculate it including the time required to spin up the drives. The real advantage in turbo mode is large files and/or many small writes consecutively .
Personally, I don't bother with using turbo mode at all. I get around 60-70MB/s over the network writing to any given array only share, and most of the writes to the array happen automatically by various docker clients, so I can't even tell (nor would I care) if a transfer takes 1 minute or 5 minutes.