I start with beaten advice to consider job change because first, maintaining productive work style was in my experience very important for professional and career growth and second, because currently you are indeed in a very good position for that.
Just think of it, any other company that would want to hire you, you can present them a requirement:
I would want to work <this way>... by the way, my current job is pretty nice except that it does not allow me to work the way I prefer.
You see, you are in a very strong negotiation position here. They can't just dismiss your requirement because if they do, they have nothing to offer to attract you (see above point that your current job is already okay except for that).
They just have to offer something to motivate you for move; it can be either confirmation that your work style is acceptable, or some material benefits ("okay our job sucks same way but we'll pay you twice") - whatever they choose, you'll have nothing to loose. The worst that can happen is they won't make an offer - but then again, it's not a big deal as you already have a job.
Besides seeking for a better job (which I believe never hurts no matter how good your current one is), the most reasonable move in your situation is to come to your boss, lay out your concern and ask for their advice.
- Learning about their employees concerns and helping to resolve these are typically considered one of the most important parts of IT manager's role. It's quite unlikely, but just in case if you find out that in your company this ain't so, then I strongly recommend you to look back to the part of my answer about job change, because this would indicate quite a toxic work environment and being a programmer you have a pretty good chance to find a better place (see eg The Rise of Developeronomics article).
Above, I used words concern and advice - and I would like to stress the importance for you to stick with these. Think of it, compared to job-change "scenario" described above, here you are in opposite, weaker position to negotiate.
To put approval of work style change as a straight requirement to your boss would be a bad idea: you have nothing to motivate them to compromise in your favor and it only may leave a bad feeling in both of you if it turns out that boss can't meet your wish.
As opposed to that, concern is safe - you simply explain your worries of how your style may be perceived by the boss and colleagues, not limiting the options to address that. Even if it turns out that they can't "integrate" this work style, boss will at least become aware that your pace isn't because you're lazy - not bad isn't it.
Now, I would like to explain a bit what I mean suggesting to ask for advice. Avoid asking boss for specific help - because you simply don't know if providing this kind of help is an option for them or not. As you don't know their options, try to keep these as open as possible - extremely broad and open ended question like "what would you advise me?" is probably your safest bet.
If they give an advice and you feel it won't fit, avoid dismissing it offhand, as this may negatively affect your further relations. If they offer something that you didn't expect but are not sure about, consider giving it a try, especially if they suggest some productivity trick.
- I learned through my career that experienced managers often know better about productivity than programmers and it's worth at least giving their ideas a try. Worst case, if it doesn't work, you'll learn that your manager is not very good at productivity techniques - it never hurts to learn a bit more about your boss strengths and weaknesses.