When re-targeting code from .NET Core 3.1 to .NET 5.0 I discovered the following quirk in a .NET Core 3.x supplied USB DLL interface code.
.NET Core 3.x interprets
