Can you be a bit more specific about what you mean by 1:! template? Your example IS a template, all be it low resolution. If you're looking for high quality art work and layout in one that's ready to print, you might find some links in the forums with a search, or just look to vendors who can provide services to match your exact needs (ie gameongrafix.com) Otherwise you need to make it yourself with an art program like photoshop. illustrator. etc and a lot of careful measuring. slagcoin.com has a ton of basic templates for controller layout that I'd start from.
In terms of a CP design, the aesthetic of your example looks nice, but there's a lot I would consider with the layout. Even with a non aggressive touch, a trackball of that size wedged in the middle is too close to the P2 joystick for comfort. You'll end up hitting it frequently depending on the game. You could consider a mini trackball perhaps?
I'd also think about the controls you want for the front end. This design is doubling up controls you probably don't need which adds expense and clutter. For instance,, why have a dedicated page up / page down for a specific front end when you have perfectly good joysticks at hand? The player is already interacting with the P1 joystick. Just seems like a lot of extra control buttons that aren't really needed. Same with the mouse left / right buttons. What will you use that for? Ideally you shouldn't need a mouse with a good front end. If a button is really needed, map P1 btn 1,2,3 for your mouse.
Now I get that you want the user experience to be clear, so there's a benefit to the grouping of controls in this example, but with some alterations to labeling you can achieve the same with fewer controls. I would also consider light up buttons with a controller and utility software like ledblinky to automatically light up the buttons used for a particular game (or front end menu). That helps make it even more clear what to press for the end user. In my research I haven't found a need for more than a "home / exit" , load & save state (optional if you don't care for it), and pause (again optional). You can also consider using a function button to get more control out of a small set of buttons (ie volume up / down).