I've experienced a couple of times now that Burst seems to take a lock on some files without ever releasing them. Although it doesn't frequently reproduce for me, it mainly happens when editing a file containing functions/jobs that are burst compiled. The symptom is that I suddenly can't save an edited .cs file, seemingly because something has taken a lock on the file, as soon as I shut down Unity I'm allowed to save again. I've been away from Unity for a while, and we recently updated from 1.7.4 to 1.8.3 so I don't know exactly when this was introduced. However, it looks a lot like this post: https://forum.unity.com/threads/burst-1-8-0-pre-2-infrequently-holds-a-lock-on-cs-files.1327899/ so I'm guessing 1.8.0-pre.2.
Thanks for mentioning this - I've responded on the other thread you linked to. Let's try to centralize the discussion there.