You're absolutely right, we'll need to fix this. Unfortunately we can never be sure whether the shortcuts we've chosen have no conflicts with the custom shortcuts on the client machine because we have to put some predefined shortcuts for our commands.
That's why we tried to do everything possible to not override some important default VS shortcuts. For example the F6 shortcut overrides the VS Window.NextSplitPane command which I doubt someone is using heavily.
What we can do is to react to customers' complaints about taking their favorite shortcut and choose some other shortcut for our command (and that's what we'll do for the F6 shortcut).
So thanks a lot for the feedback and should you have some other concerns or suggestions please don't hesitate to contact us.
the Telerik team