As already noted by Jon, the Etherchannel hashing algorithm is unique to the transmitting device, i.e. it doesn't matter what the receiving device uses for it's choice (except as already noted by Jon, you want what's optimal for its data sending).
As to performance issues, again as already noted by Jon, that depends on what's "best" for the device transmitting. For example if on one side you have a server and and on the other side many hosts, the server side transmission might use dest-mac or dest-ip, and the hosts side transmission use src-mac or src-ip (generally, you're looking to avoid using the same attribute values for multiple flows). Or, both sides might use something like src-dest-mac or src-dest-ip. (NB: your WLC's default [?] of src-mac might be a suboptimal choice. The 9500's default [?] src-dest-port would probably be good for just UDP/TCP traffic.)
Between two hosts, you might look for something that uses IP UDP/IP port values too, but generally only Cisco's top line switches support that as an algorithm.
Some additional notes: a single flow will only use one link, loading is not dynamic (i.e. a busy link will not take advantage of a non-busy link) and load balancing often works out best with powers of 2 [2,4,8] number of links (although some later switches now distribute better over non-powers of 2 number of links).
