No I wasnt able to reach at a viable solution at the time last tested.
As per their response,
"The problem now is, there's a bug that stops the filters properties from working, check validateReportLoad incorrectly returns schema errors for valid filters. The workaround is, as your mentioned, set the filter after loaded"
The bug could have been fixed.
But if you are implementing it correctly and yet not able to get the filter in place, then lets conclude the bug still exists.
You might want to try the workaround I tried mentioned in my query itself, although it wasnt a viable solution for me