My advice is to methodically reduce your sketch down to the absolute minimum amount of code required to still produce the problem. Often once I have done that I find that the problem is obvious. Even if it's not, that minimal demonstration sketch will make it easy for the forum members to help you out with it.
Well, I think it's important to keep in mind that people who had a great experience with a product are much less likely to be motivated to post about it.
It's also important to keep in mind that a complaint you read about one MKR board may not apply to another. For example, there were some problems with the MKR GSM 1400 hardware design. But those problems are not at all relevant to the MKR WiFi 1010.
If you want the highest possible level of community support, the AVR architecture boards (Uno, Nano, Pro Mini, Leonardo, Micro, Mega) are the best choice because they have been around the longest. However, the support for the SAMD architecture of the MKR WiFi 1010 is pretty well supported too. It's true that new bugs and incompatibilities have been introduced into the SAMD core library over the last year, but those happened during a major refactoring of the core that will greatly facilitate its ongoing development in the years to come. During that same period no new bugs or incompatibilities have been introduced to the AVR core. The reason is because there hasn't been a release of the AVR core, and not a lot of development on it either.
The specific problem you are having would likely also occur with the Leonardo. The symptom would not occur on the boards without native USB capability such as the Uno and Mega because those boards have a dedicated USB chip which can not be affected by the code in your sketch. But that native USB capability has several benefits as well.