Why Were SYSLIB Warnings Introduced Separately from CS0612/CS0618?

The CS0612 and CS0618 warnings are specifically related to Obsolete attributes. These attributes are tied directly to deprecated APIs or types and are typically used by developers when they are marking their own codebase for future removals.

SYSLIB warnings, on the other hand, are part of .NET’s internal library warnings (System Library). These warnings:

• Reflect system-wide deprecations that affect larger parts of the framework. (i.e. they will be gone forever after a certain update)
• Help developers transition from obsolete technologies or practices that will be removed or replaced in future .NET versions.
• SYSLIB warnings are specific to the Base Class Library (BCL) and are meant to convey broader framework-level changes, such as serialization patterns, encryption policies, or formatter-based serialization.

By using SYSLIB codes, Microsoft is able to provide more context and clarity on specific categories of deprecations, distinct from the more general-purpose CS0612/CS0618 warnings.

https://learn.microsoft.com/en-us/dotnet/fundamentals/syslib-diagnostics/obsoletions-overview

I believe this post should help you, as you are just doing the reverse of what he is doing