Yes, I have looked into those. But as far as I can see, by modifying those properties I can get all the features in a single request, that is, in a single page. However, this will always result in two requests to the WFS service where there used to be only one request.
I load data from WFS as the user moves around on the map, so there are potentially lots of requests firing. Setting the maxPageCount to 0 seems to have the same effect as setting it to 1. In many APIs setting parameters like these to 0 or -1 etc. results in disabling the feature. That is what I would like to be able to do as well. Without the ability to disable paging, I always get the "RESULTTYPE: hits" request first and only after that the actual request for the data. Looking at the network log in my browser I can see that a lot of times the "RESULTTYPE: hits" request is as slow or even slower than the actual request for the data.
