A simple workaround that has worked for me:
I had a project where we didn’t realize it wasn’t compatible. So, I switched the Metabox Icon field to a text field.
Once you switch to the text field you can output it in a Basic Text (or any text element) in Bricks using standard Font Awesome HTML:
<i class="{dynamic data here}"></I>
Replace {dynamic data here} with your MetaBox field.
You can then style the text element however you like directly in Bricks.
It’s not ideal but it works.
Finally, it looks like this made it into the 2.0 (currently alpha) build. Bricks 2.0 Changelog – Bricks – “Metabox and ACF Icon field integration” 
Hi guys,
Yes, we added this improvement in Bricks 2.0 alpha, now available as a manual download in your account (see changelog).
Please let us know in the bugs category if you are experiencing any issues.
As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.
@timmse Is there any documentation on how to use this?
No, but it is as simple as any other dynamic data tag:
You can add the dynamic data to an icon, SVG, or basic text element, for example.
Yeah my bad, I forgot to put the icon element inside the actual query loop. Working great now! 
