CPM with custom Project SDKs?

[TheXenocide]

We use our own custom Project SDKs to centralize a lot of MSBuild/NuGet functionality that is reused across many different repositories/solutions. I was looking into some NuGet behaviors we were hoping to improve in our SDKs when I discovered the Central Package Management functionality, which looks to be a more mature implementation than what we're doing currently (loosely based on CPV using <PackageReference Update=...>). I was wondering if enabling CPM and defining PackageVersion items in a custom project SDK is supported? As I mentioned, we don't really want to duplicate all the package versions from our custom SDKs into a bunch of separate repositories, but if we could change all of our <PackageReference Update=...> items to PackageVersion and then use CentralPackageTransitivePinningEnabled feature that would be a huge boon for us (as of right now we have to manually manage transitive conflicts in individual csproj files and we've been discussing various tooling options for helping us better detect them and/or automatically inject them via our SDKs, so stumbling on this first-party functionality comes at a really good time).

Before I invest a bunch of time on this, does somebody by chance already know if this is considered supported?

Maybe better suited for its own discussion, but do <PackageVersion> items support .* versioning? This would also be rather important to us (and seems to be an oft forgotten functionality as new features/standards are developed, though it works very well for a lot of our needs). These features in conjunction would really clean up a lot of our NuGet implementation.

Edit: Seems .* may not be supported, according to this discussion