It is definitely not a self imposed misconception. You know I have read many posts where someone struggled with some part of code not working right on either esp32 or other boards, and after mentioning it, someone found an error with the code and corrected it.
Someone was having a freezing issue after receiving 512 bytes, and Cattledog was who suggested increasing the bluetooth Rx buffer size. So simply saying "it's what it is, nothing can be done" is not the way scientist and technical people go about things. How do you know my problem isn't being cause by an error in one of the bluetooth definition files, and it can be fixed in the next update. You have heard of software updates that fix systemic issue like that?
I am honestly tired of arguing about this with you. I have heard your input and your opinion regarding this problem, why not leave it to get more opinions, if you heard someone's opinion, would you nevwr seek a 2nd opinion? I'm not convinced it can't be done, especially since I know it can be done. I will try to get more opinions or see if anyone else might have a solution.