And if the streamer is welcome for your bot to perform actions that require additional permissions, the streamer can grant those permissions. An account being a mod in a channel doesn’t automatically mean you can delegate everything you can do first party (ie, logged in as that account on Twitch), to another 3rd party.
While you may be that 3rd party yourself and control the bot, if you connect to some other 3rd party app you can be granting some controls over that channel to someone that the streamer knows nothing about as they have no clue what connections your bot account has to apps that the streamer may or may not want.
Twitch disagrees.
Again, please stop confusing 1st party and 3rd party. Also verified/known status doesn’t grant your bot any special status beyond the intended use which is a higher rate limit. My personal account has verified bot status, as does many others, doesn’t mean we should get more control over a broadcasters channel.
If the reports aren’t actionable it’s because they are not doing anything that is against Twitch’s ToS, Community Guidelines, or any other applicable legal agreement.
As for UserVoice, most of the feature requests are by either individual developers, or small teams, as are the ones that have been successfully implemented. If you look through UserVoice and filter it to completed you’ll see that smaller devs are listened to and their suggestions acted on. The most frequently successful feature requests are those where there is a clear and well explained use case, where as simply not being willing to have the broadcast auth to your app and grant the permissions or saying ‘but I can do x, y, z, on the Twitch site itself!’ may be weighed less heavily against the downsides or development/maintenance time required for the idea.