Yes, this definitely comes up. It makes sense it is the way it is for auditing purposes and so that one person doesn’t take an action while another changes what it does, both affecting each other in a non-obvious way.
This one is a bit odd too. There really isn’t a difference, except that there is, and it is really about default behavior.
We often create something as a fixlet or task based upon organization within the console, and not normally about the desired behavior since most of our custom content is designed to
be considered successful when the applicability relevance evaluates to false.
Generally I tell people that a fixlet should be something that is expected to be remediated, while a task is optional or repetitive, but ideally all content would have good relevance that goes to false after it completes if possible.