If the crawler requests a URL the server returns the current cache status when a url is requested. This is always "miss" or "blue" if a URL isn't cached yet. Run the crawler again and the status is hit or green.
In short, yes, because there are a lot of many other features you should care. An overload is often caused by PHP and MySQL issues. quic and the protcol used don't compensate any PHP and MySQl leaks.
I think you are over-emphasizing quic and http/3 detection, as it does not provide any significant benefit that could be leveraged by your programming.
That's all well and good, but how are you going to convince your clients that identifying quic and http/3 is so much better that your work deserves payment?! Maybe you know more than I do, but I don't know of any way to prove the difference?
And what advantage do you hope to gain from this? The use of quic primarily serves to improve the deficits in connection establishment with https, because the TCP protocol tends to neglect SSL. Wouldn't it be better to focus on http/3?
Nevertheless, I don't understand how you can use PHP to...
LiteSpeed does not change anything or cause any problems that affect ranking. If you notice problems with your site's ranking, check your site with Google Webmaster Tools or Google Search Console: https://search.google.com/search-console/
LiteSpeed Wiki is very outdated and only contains information up to version 5.3. You should therefore look for relevant entries in the documentation.
https://docs.litespeedtech.com/lsws/extapp/php/configuration/modes/