Yup - you can use anything you like, it doesn't have to contain the word 'controller' anywhere in the class name. I just used that in the example because it's probably a pretty common pattern for those sharing such classes between applications.
I was following the Device Profiles guide on the ST 2.0 Docs and realized the fully qualified paths for controllers and views do not work. They just get appended to the standard path, ie: "app/controller/tablet/MyApp/controller/Main.js".
I spent quite a few hours trying to see if I did anything wrong (since according to the guide, using fully qualified paths should work)... until I came to this thread.
So I'm also wondering if there's anything we can do about it besides waiting for the next release.