I can't help as A) I didn't understand the problem as it was outlined in the other topic started by the OP and B) I don't have avast Pro, so I don't have the SafeZone and SafeZoneBrowser, so can't test.
If I had a problem then you would hear me holler.
That said I don't know if gdiloren had the Outpost Web Control module enabled.
The Outpost Firewall Pro Security suite even with the AV remover or custom install and not installed would potentially leave other modules. So the Outpost web control & avast web shield could conflict. Add to that running in what is a sandboxed environment of the safe zone and I think there is potential for conflict all round, as the Outpost firewall also has some sort of sandbox feature, see image of a search in the C: drive for sandbox, all of these files with the exception of the outpost sandbox.sys driver are in the Outpost program folder.
Now we are possibly getting into the area were someone was having a problem running an application running under sandboxie inside the avast sandbox. Here we are getting into dangerous conflict territory.
So I really wouldn't know where to start with this.