Has Apple Acknowledged Memory Leaks Mac Mini M1 16GB RAM. Perpetually Dismal Performance.

I'm using a Mac mini M1 2020 with 16GB RAM. I have had nothing but trouble with the BT connection on this Mac. But while this issue was common in the early years of the M1 Mini it seems that the BT issue is resolved with progressive OS update ... yet for me these issues persist. Over the years I have consulted with Apple ... they had some geek contact me and run some scripts for me to give them feed back but I never heard more from them. I've brought the thing to an Apple Store and they found no problem ... BT worked just fine in their store. But the issues still persist. To surmise ... I cannot use a BT keyboard or mouse of Apple or other brand on my mini. The connections lasts only a few seconds. Apple headphones connect but often lose connection ... simply when I turn my head and Im literally only 3ft away from the mini. I have had better success with Logitech mouse and keyboards using a Logitech USB antenna BUT even these play up when I am really busy ... i.e. using the mini with multiple apps. In particular, MS Word with pasted in graphics, WhatsApp, Safari on YouTube and on FB, iMovie with large files and most common failures happen (I think) while other heavy tasks are being conducted in the background ... like backing up processes. By failure I mean mouse jumps or lags or keyboard seems disconnected and or severe even distorted relay of keys typed. The quick fix is to disconnect and reconnect the logic dongle ... least for my input process ... BT still is of no use alternately and any time ... but App processes often stall ... cut and paste won't work (sometimes due to keyboard disconnect) but sometimes cos their is overload on the RAM. I often get running out of RAM warnings from my "Clean My Mac" App. I have come to the conclusion that memory leak must be the culprit over and above the BT issues. Most frustrating is that I am unable to demonstrate this to Apple ... it does not happen when you want its to ! Does anyone else have this issue and has there been a fix or any acknowledgement from Apple ? Unfortunately in my neck of the woods Apple won't look to fix something unless you can demonstrate the problem.