"This browser behavior cannot be prevented and I am afraid that I cannot suggest a suitable workaround for that case. If the table element is not focused other Grid features may behave unexpectedly."
Actually that's not the end of the line here. While the problem is that kendo is calling table.focus(), and that the browser will scroll the table into view during focus, you can "prevent" the scrolling by resetting the scrolling right after the focus call. In fact, when I went to patch kendo to implement this in the source code, I was surprised to see that kendo actually had written code to do this already! However, this code is only in 1 of the 2 focusTable() functions (why are there 2 functions?).
I have a patch that we have made and are using here that I would like to suggest back to the code base. Basically I just took the implementation from the 2nd focusTable() function and applied it to the first focusTable() function and it's working great! Essentially what it does, is right before it goes to call table.focus(), it loops through the parent elements of the table and determines which of them are scrollable. Then it stores off the y scroll value for each of those elements. After the table.focus() gets called, it just re-applies those .scrollTop(y) values to each of the parent nodes. Since this all gets run before the browser does a repaint, you don't even see the page scroll at all.
How do I get a patch to you? I'd like to open a new ticket to get this addressed, but I wanted to comment here as well. We are currently using KendoUI 2014.3.1215.