Hi @Spork,
I can finally confirm that with version 2.2.2 the issue has been resolved. 
I would like to point out that, contrary to what I previously assumed, the issue in this post does not seem to be related to the issue
As always, thanks for the support. 