I'm not sure if you are going to gleam much from this in terms of optimization with the exception of partner ops/kbs. Those should be at or near 0 unless you've good paths to your hosts for some reason.
Another thing that is more interesting would be to zero them out and then look at what you're getting over a smaller amount of time. 3 days isn't very useful. The command may have a -z flag to zero out the stats.
Otherwise you'll have to do the math yourself.
But just telling you how many ops you are doing is nice, but probably not the best in terms of optimization.
I'm saying that whatever you hope to glean from those particular stats are usually more meaningful over shorter time periods. This is especially true if you make some change. The effects of that change or lack thereof are more evident that way.
However, I'm still not sure what you are looking for here.
Hmm...that's tough when you don't necessarily have a problem or a good basis of comparison.
My best recommendation would be to get a hold of the best practices guide for Exchange 07 on NetApp and ensure that you are following as much of that as possible in your environment. It should be on the external site in the Library. Or your SE should be able to get one for you.
But just looking at lun stats other than partner ops may not tell you much as your the raw ops will depend on the load, etc.