Avoiding typing by stuffing things into the most convenient corner without regard to what it is officially for is a fast road to a bad design. If the things in question fit into the role, then load as many as you want. If they are not logically part of the role, don't do this.
in reply to Moose Role to include Use statements
However I would not object to creating a new module explicitly to give you all of the utility stuff you want. Name it something like StandardModules and use that instead. That will make it more obvious to the next person where you might be getting random stuff from. (But be very careful about putting things there, because they are going to pollute every namespace.)