The rule of thumb is to exclude nothing, unless you have to.
And, if you have to, utilize the flexibility of the scanning configuration to create as small a hole as possible.
For the latter, that could mean only excluding writes, or reads of specific files or perhaps a file type (database files for example should be excluded from both read _and_ write scanning).
Better still is to leverage the hi/low risk profiles, giving more granularity i.e. applying exclusions to specific processes only, again for Read _or_ Write when possible, both if appropriate.
Applying these concepts to the MSFT recommendations you can create a sound scanning configuration.