Nope. today memory-infra dumps lot of data and impose some overhead (in terms of adding jank). It would go against the spirit of default categories, specifically, would kill all the use cases when people want to grab performance data for a long time frame, as opposite to lot of data (like memory) for shorter time.

Also due to the bugs I'm solving as part of bit.ly/TracingV2, it is "lot of data" per event, so events are not dropped out of the circular buffer. As such, we end up with very large traces which then can fail to import.
They are all very sad problems that need a resolution. However, until we solve them memory-infra cannot be a default category.