You are asking as the real goal was to use MVC for the sake of using MVC. Yes, it can improve maintainability of your project and other qualities, but the whole approach is wrong: you need to come from the goals of your project itself.
The situation would be very different if you tried to create some alternative to MVC, some new architecture or a new framework. But you merely want to use MVC which was already created for you before. So, perhaps you should remember that it was really created for your project (among many other ones), not that your project was created for MVC.
So, your questions display some trace of your, in a way, upside-down view. Let's see: 1) It's likely to be reasonable, but it really depends on your project goals and requirements. 2) I would not be afraid of challenges; it would help you to deal them as you face them; this question is weird because you should understand that we know very little about your skills and resources.
Now… 3) issues with browser compatibility? oh yes, issues, issues and more issues. I would say, they are not much related to MVC itself, they are more about CSS and layouts, and also about avoiding all non-standard or purely supported JavaScript and DOM features. My key idea here is: don't try to achieve identical look; this is nearly impossible. Instead, develop UI design which keeps your unique look and feel and yet is not too sensitive to different rendering detail of browsers' layout engines. Please see my past answers:
webpages layout change when running in different browsers.[
^],
How Do I Convert Desktop Site Into Mobile Site[
^].
… 4) not clear what you mean by that; download the MVC framework and read the requirements; 5) yes, but, again, it depends on your project (imagine what could happen if your side is just one page :-)).
—SA
Submit an article or tip