I think you'd need to look at both.
Currently, party compositions are enforced based off of LB penalty and damage bonuses. You take additional penalty to LB generation for each violation of a standard composition that you have (i.e. solo tank, solo healer, or duplicate jobs). You gain 1% damage for each unique role you have present. Creating a combined Ranged category would mean that you could bring any combination of two out of seven Ranged jobs that you like to meet these requirements. This also would mean that jobs within this Ranged category would only need to be balanced internally against each other in terms of utility, and that you would stop penalizing jobs for bringing utility.
A revision to the role action system would help with this as well. The current system is archaic and has a lot of genuinely strange actions that have niche functionality. For an action to be designated as a role action, it should be something that you want to remove from balance considerations, because everyone has it. Raise is a good choice for this. Right now, Raise jobs are progression jobs. They do less damage, and then you swap out to a job like PCT to meet the DPS check. At the same time, you can't really get rid of non-healer raises, because if both healers go down in casual content you need a way to get one back up again for LB3.
Because Raise presents a balance problem, I think it would be a great candidate for a Ranged role action. That way you have standardized access to Raise and a fixed number of Raise providers, so nobody is penalized for bringing it. Just call it 'Phoenix Down', and give it a fixed recast or set number of uses depending on content difficulty. Now it doesn't influence job balance. Raid mitigation tools and % healing buffs are other things that you could standardize as well. Raid movement tools are another. Petolon is restricted for out of combat use only. What if it was a Ranged role action that provided a short duration group movement speed buff, like Expedient? Role actions allow you to incorporate really powerful effects without worrying about individual job balance, because everyone has access to them in a consistent way.
You'd have to decide about what to do with Swiftcast and Lucid, but I think these can easily be integrated in a job specific fashion to Ranged jobs that use them.
In short, just rework the Role Action system so that 'mandatory utility' is role dependent rather than job dependent, which removes the need to penalize individual jobs for having access to them.