hmm interesting. P3 works differently on a Local Development server vs a Live Hosted server. My previous testing was done on a Local Dev server. On a Live Hosted server I tested these scenarios and these are the results.
Simple History consistently uses a range of .13 to .18 plugin load time seconds and if you are looking at the usage percentage (Plugin Impact of page load time) then that is going to throw you off. The total Plugin Impact percentage is relative to everything that is loading/being used and should not be looked at like overall website/server resource usage on the website/server. Example: of the total percentage of things loading X is using X%.
My theory about alphanumeric ascending plugin name ordering skewing results for the last alphanumerically oriented plugin is incorrect/wrong. I installed WooCommerce to test that theory and then other plugins to test and disprove that theory. ie higher and lower alphanumerically named plugins. What does occur is that the usage percentage decreases for Simple History when you install more plugins because the usage percentage is relative to the total number of things installed that are using resources, but Simple History is consistently within a range of .13 to .18 plugin load time seconds. Overall executed Queries is well within the acceptable/good range.