Disable force-respawn of memcached upon certain configuration changes

Given the addition of the GIO and bucket priority in 3.0, I would like to ask that we disable ns_server's forced respawn of the memcached process when the following items are changed (and therefore allow them to be changed if they cannot currently):
-GIO thread count
-Bucket IO priority
-memcached connections
-memcached worker threads
-ejection policy

These are very frequently tuned items by the field, support and customers and it would be extremely helpful to allow the new values to be "set" but not yet applied until either a memcached restart occurs or a new node is balanced in