I'm what I consider to be a user that doesn't "stress" the editor, so therefore I'm unlikely to see the sorts of bugs I can usefully test and report. I also don't install the kitchen sink, so there are far less chances for bad interaction between things. The most chance I've had to test something that might (vaguely) have affected me was with the recent dired-killing-frame-on-start bug (#65277), and I don't normally start emacs with a dired session anyhow.
In regard to release cadence, I'm not really bothered how long the product (in this case, the new version of an editor with new functionality) takes to produce. I just want it to be stable enough to work when I compile and run it. I'm not honestly sure how you'll get useful aggregated information out of my class of users, any hints here? (Aside from that of simply getting more involved).