Here's what we did at a customer to help with this.  We increased the number of IPs per pool and interface, which would allow us to rebalance the IPs per interface.  Once that's done, we can move the IPs based upon the policy set (Connection Count, Throughput, etc.).  The command to achieve this would be “isi networks modify pool--name : --sc-rebalance”.  The will move IP around in the cluster.  
Customer would like to distribute all client connections across the nodes with most resources available – this would make using “CPU Usage” as the best option for this setting.  The concern is if they set to “CPU Usage”, when they reboot the servers on the weekend(s) when there is little to no activity, how will the cluster redistribute the client connections?  Also, once they start to ramp up during the week, what if the busier clients happen to be on the same node/IP Address, how can we then redistribute those client connections?
How do I evenly distribute IPs on a cluster with SmartConnect after client 
reboots?