yes it's a limitation of Power Query Salesforce Reports connector. similar kind of a connector is available in Google sheets as an add-on that addresses this problem.
Many product api's come with this kind of limiation of allowing to read not more than x number of records in a single api call. It's upto the connector (like Salesforce report connector in Power Query or Salesforce data connector in Google Sheets) to do the recusive calls to the api until the last record is read through the api.
Google addressed it in its Salesforce data connector of Google sheets. Microsoft hasn't addressed it yet in Power Query. Moreover, it's not a huge development effort for that enhancement of reading full report data. It is just about turning that api call into a recursive on until all records of the report are read.
Does Microsoft really need votes for it? Prioritization doesn't necessarily had to be through votes all the time. Folks are posting solutions to extract full report data using google sheets and then consuming it into the power query from google drive using web api like here:
Solved: How to Bypass Salesforce 2000 Rows Limitation - Microsoft Power BI Community
These are the loops that are driving people to see the alternate vendor solutions.
same idea posted as another one here too: Microsoft Idea (powerbi.com)
Recent ideas
Allow setting default scroll position in Table and Matrix visuals (e.g., start from rightmost column
Currently, Power BI Table and Matrix visuals always open scrolled to the leftmost column by default, which is inconvenient for reports where the most important data is on the right side. Please add ...
