PRs are triaged more often than issues, as these contain actionable data (new code) that can be decided on. Issues are one level away from actionability. If there are still useful PRs or other useful work, you don’t just jump in and spend 5 hours responding to (mostly not actionable => “useless”) issues.
If you actually want to help, feel free to go through the issues as well and help out. Not only on ones that you create, but also on the ~250 from other people. Help the users, tell them to close the issue if it actually isn’t relevant (any more) or correct. This will help a maintainer to actually have something to work with when they decide to spend some time on issues.
A well written response from a reputable user like you that actually describes the problem that has to taken action on, maybe already with some ideas about solutions etc. makes it much easier for them to tackle these with actual work, and not spending hours copy pasting “What is your
ionic info output? What version are you using? What are you talking about? Can you build a repro project and upload it on Github?” responses.
(I write, after spending 3 hours responding to forum posts and issues of the projects I contribute to… instead of actual coding.)