A lot of stuff to attack here
Adaptive Flash Cache (AFC) can do RAID0... from 3.3.1 I think. On the other hand I've never been happy with AFC. In my testing, AO always reduced traffic on FC the most and if you don't have NL then it will only support data on FC tier. Some scenarios AFC makes a whole lot sense, but generally you're better off letting AO do the trick.
As for AO and min_iops... with FC and SSD I always set min_iops to 0 and set a t0 min on AO config. That ensures that you're always putting the most active blocks on SSD even if the usage is low. As long as you don't have NL, nothing will get worse performance but a lot might get better.
For RR and iops=1. I'm not sure what your reference is, but 3PAR is active/active so your IO will be processed at the path it is sent. For active/passive arrays, RR will ensure that 50% of the IOs are recieved on one controller and processed on another. You seem to have a small environment so it might not matter but for larger arrays setting iops=1000 might cause hotspots in the SAN and on host ports on 3PAR that give variable latency across paths.
As for DelAck. Test it. If you see a difference, disable it. If not, don't. As for 10GbE gear for iSCSI it is often more important about switch port buffers, than pure speed. It seems that everyone forgot after 1GbE.