Problem with runtime async in .NET 11 RC1: unexpectedly larger binary size

### Description

I have a [small program](https://github.com/HotCakeX/Harden-Windows-Security/tree/main/AppControl%20Manager/eXclude/DISMService) that uses .NET 11 RC1 which is controlled [here](https://github.com/HotCakeX/Harden-Windows-Security/blob/main/AppControl%20Manager/Directory.Build.props) and [here](https://github.com/HotCakeX/Harden-Windows-Security/blob/main/AppControl%20Manager/global.json)

Normally, the binary size is 1.55 MB, but after adding this line
```
$(Features);runtime-async=on
```
The binary size is 2.12 MB

### Reproduction Steps

1. Publish the program for X64 architecture
2. Observe the binary size with and without runtime async feature.

### Expected behavior

Binary size either remain the same, or slightly vary.

### Actual behavior

Binary size increased unexpectedly, rooting many new things.

### Regression?

_No response_

### Known Workarounds

_No response_

### Configuration

_No response_

### Other information

Visual Studio 2026 Insider
Windows 11 25H2

Start with the linked AppControl Manager/eXclude/DISMService program, then inspect Directory.Build.props and global.json for the .NET 11 RC1 and runtime-async settings. Publish the program for x64 with and without the feature, compare binary size and rooted items, and determine why the additional roots appear or what expected behavior should be documented.

Written by the indexing model from the issue text.