The views.view.*.yml configuration file in the module does not define a cache: setting. This means the View uses no caching at all, which negatively impacts performance and bypasses Drupal’s intelligent cache invalidation system.
The View configuration should define caching using cache: type: tag, which is the recommended default in Drupal 9 and 10. This enables automatic invalidation when messages or related entities are updated.
Active
1.17
Core
those views are not built with caching in mind, there are custom plugins that aggregate stuff that will not be properly reflected.
Caching is only sensible if it it's viewed a lot more than it's invalidated. That's quite unlikely on these views.