Nope, unfortunately. Thank you for your continued help, seriously. It’s unfortunate that this will take so long to fix upstream, but I’m also glad that we finally caught their attention. Hopefully, .NET Core will become more useable with Snapcraft. Currently, with .NET Core 3.1, I’ve been using a modified dotnet plugin that someone wrote in a Launchpad issue a while back, to build with snap, as the official dotnet plugin has been known to be broken (unless this has changed quite recently). I’m afraid that by the time 5.0, or even 6.0 come out, this modified plugin will itself become incompatible, creating yet another issue. Maybe I should learn Python to fix it myself, if this happens 
?
EDIT: Here’s where I found the custom plugin: https://bugs.launchpad.net/snapcraft/+bug/1857705. The bug with the official plugin was marked as triaged and of high importance, yet was not resolved back in June when I first looked into publishing on Snapcraft. If this has been fixed it hasn’t been marked as such.
If it has not, I suggest accepting ed10vi’s patch, which was written toward the end of May, ASAP and then looking into ensuring the dotnet plugin continues to work with future releases. .NET 5 releases rather soon, November 2020 (release previews are out now), with 6.0 being targeted for November 2021 (source).