Yes. I do want to fix the underlying problem (allowing snaps to specify their exact desktop file ID when it forms part of an API):
I’m not sure when I’ll have it fully sorted out though. The primary use case I’m interested in is APIs that are built on top of D-Bus activatable desktop entries, such as the GNOME 3 notification system. In this case, the name of the desktop file must match the D-Bus name the application acquires.
It has been on the back burner for a bit though, since we need to allow snaps to provide D-Bus activatable services first.