Are the other controllers DCs for child domains, or are they additional DCs at the forest root level?
If they are additional DCs, you SHOULD be able to transfer ALL 5 FSMO roles that the forest root DC has to one of the other DCs. Once this is done successfully, you can then demote the server to member server by running dcpromo. This SHOULDN'T affect the operation of Exchange in any way.
Having said all that, I have the following suggestions: Making any substantial changes to the forest root DC can obviously have major consequences (like having to recreate your entire AD forest) if things go wrong. Assuming everything is functioning adequately as it presently exists, unless Exchange is impacting the operation of your DC (as a DC)(or vice versa), I would recommend leaving well enough alone (this would definitely be a case of "If it ain't broke, don't fix it!").
One other option would be to demote on of the other DCs, install Exchange as an additional Exchange server, move all information stores and other Exchange functions to the new server, and remove Exchange from your current forest root DC.
If you are set on seperating the Exchange and DC functions, which route you take (move FSMO roles, or move Exchange) should only be decided after a thorough risk analysis. Factors to consider: if you attempt to move the FSMO roles and AD gets corrupted to the point you have to recreate your forest, you will also very likely have to reinstall Exchange, as it is verydependant on AD for its successful operation.
Hope this helps.