I understand this can be a frustrating issue - it is caused by Chrome reporting a wrong Content Type when pasting an image. Since DeskApp makes use of the Chrome engine, it is also affected.
It is not easy to work around the problem, making an assumption about the Content Type might also affect other content. If we would wait for it to be in the 3.4.19 release we would have to delay that further.
Edit: I should add by the way that this KW-2443 does not affect functionality, it is only the content type which is incorrectly registered. KW-2443 implements a permanent fix for the workaround that was implemented. If you do experience broken images etc. this is a different problem and should be looked into separate from the development ticket you reference.