Depends on how fast you want the algorithm to run, how precisely you want the detected peak to reflect the actual peak of the fitting polynomial, and how well your fitting polynomial actually models your data/system.
You could just find the max of the resampled polynomial, but to obtain the equivalent precision of the Peak Detector, you would have to sample at a very large number of points. For example, if you want three decimal places using just the max of the resampled polynomial (no call to Peak Detector.vi), and the domain is [0,1], then you should resample using at least 1000 evenly distributed points. To get 4 decimal places, you need 1E5 points. At some point it is more efficient to coarsely resample the polynomial an
d use the Peak Detector.vi. The resampling that I implemented before the peak detection step was not really optimized for the smallest number of points. My rule of thumb is to resample until the data is "relatively smooth", or the peaks/valleys in the data are separated by 10 or so points. I used 500 points, but could probably have gotten away with 50, or perhaps less. You should be able to play with the VI and adjust the number of points that are resampled before the peak detection step downward, and compare to the other method. Continue to decrease until the two answers begin to diverge and you will have a lower limit for the number of points (for that particular problem).
Regardless of which approach you use you are still constrained by the accuracy of the initial model fit. If a third order polynomial does not model your data well, then all you will be doing is very precisely finding the peak of a poor approxiamtion of your original data. Anyway, good luck.