In those cases, I usually guide toward a dashboard with two reports to contain requests and projects separately. In our environment, the information that people want to see in the report about requests only partially overlaps with what they want to see about a project. For a request, they want to see who requested it, ETA for delivery, whether it's client-facing or internal etc. All facts that wouldn't exist in a project report - so you'd have 3 entirely blank columns taking up screen space.
That gives me one 'view' but allows greater customization of what information they actually see in the layout. Not sure if that makes sense in your use-case, but food for thought.
If they REALLY want one single report, the work-item report type that Samantha suggested would do it but you'll be somewhat limited to the facts you can display in the columns - so I'd suggest trying a mock-up of what your leader wants before promising it can be done. (Voice of painful experience)
