I think it is more productive to start from real issues or broken functionality rather than investigate all available exceptions from RuntimeLog. It doesn't hurt to take a look, but if exception doesn't correlate with real problem and doesn't ring any bells then you shouldn't put a lot of time into it right away. Just be aware it exists in case you get unexpected problems later.
Benign exceptions that could occur in a log would include adapter exceptions. Those exceptions happen deep within the automation engine and are handled but reported for your information. You may suppress these exceptions from raising a message dialog in the RuntimeConfig.xml file but the exceptions will still be written to the log. Additionally, if you handle an exception with Try..Catch an exception it will still be written to the log. As Konstantin stated - "start from real issues or broken functionality". You may not be able to fix all of the issues, but you can put in exception handling so that your automation will function as required.