Not a malfunction. AWStats just shows whatever the browser or bot sent in the Referer header. Some spam bots put fake values like http://email@domain.com there to get their address or domain into public stats pages. Real visitors almost never send that. If it bothers you, add the pattern to SkipReferrersBlackList in the config (or a referer blacklist file) and it will be ignored on the next update.
If a manual run sits for over an hour, the lock file is probably just a symptom. The cron job starts every 6 hours, the previous run is still busy, so the new one finds the lock. Two things I would check: DNSLookup in the config (if it is 1, set it to 0, reverse lookups on a big log can take forever), and whether the log was rotated or replaced so AWStats is now reading a huge file from the start. Once one run finishes cleanly the lock goes away on its own.
You are right, and it is not really something AWStats can fix from the log alone. Windows 11 browsers still send Windows NT 10.0 in the user agent, so the old windows nt 11 pattern will almost never match. The only way to tell them apart is the Sec-CH-UA-Platform-Version client hint, and Apache does not log that unless you ask the browser for it with an Accept-CH header and add it to your LogFormat. Without that, treat the Windows 10 row as Windows 10 and 11 together.
In case it still helps someone: the name feed comes from the generic list at the bottom of robots.pm. AWStats matches parts of the user agent, so any agent containing the word feed (Feedly, FeedBurner, Feedfetcher and so on) gets lumped into that one row. Your awk filter drops every line with mozilla in it, and most of those feed readers include Mozilla in the string, which is why it never showed up. Try grep -i feed access_log | awk -F\" '{print $6}' | sort | uniq -c | sort -rn | head and you should...
Yes. In the AWStats report, look at the Pages-URL section in the left menu (under Content / Viewed). The main page only shows the top entries, but click Full list and you get every URL with its page views, entry and exit counts. You can also use the filter box there to narrow it to one folder, for example /blog/. In cPanel it is the same report, just open the domain in AWStats and scroll to Pages-URL.
If this is in the Robots/Spiders table, the number after the plus sign is the hits that bot made on your robots.txt file. AWStats counts those separately from its other hits. So 47,502 normal hits plus 83 requests for robots.txt. The small legend under the table says the same, but it is easy to miss.