Your boss talking about "new talent" sure sounds like he wants you to bring in a jr. developer as an innovation factor, to add the certain "something" to the project.
What I think is that he is wrong (don't tell him that, though...). Software, even when considering innovation and talent and fresh ideas, needs those things in advance and has to be well planned out. Good software is planned software. Whenever you just go 'n write stuff, it will, at some point, bite your a*s. We had some Facebook link here a few days ago which stated just that: Facebook has some 500 developers working on some 180000 classes just for the iOS app, which really is hardly more than a simple news-feed with comments. Instead of fixing the root of the problems, Facebook just throws more developers at the problem.
Don't be Facebook. Instead, program the stuff you planned the way you planned them. Don't go and get a new "talent" with their own ideas how to solve problems, who "hack their way and move fast". It's too late for that and it will result in problems. The only thing you might ever consider is a "code monkey": some person who implements stuff exactly the way you tell them to (without thinking about it).
What you might tell your boss, though, is that a new "talent" might be a good idea for a new project or once you released the current product and want to think about new features and improvements.