That's an interesting question, and I don't have an immediate answer as I am not familiar with BoatBeacon. I presume that you have it set up to read data from the Yakker (as the source of local AIS data) and it then combines that with internet derived AIS data into a single feed?
I gather from the website that you can make an in-app purchase within BoatBeacon to allow 'AIS sharing' which then re-transmits the combined data for reading by another app (eg Navionics). It sounds like you may already have this, and it should work with AngelNav too by pointing the latter to BoatBeacon's IP address instead of the Yakker.
The open question is whether the code in BoatBeacon also sends instrument data. AIS messages are just plain old NMEA 0183 messages with coded content, so if BoatBeacon is relaying the AIS messages, then it may also relay the others too (In fact from a coding point of view they would have to positively write code to NOT do this!).
So my suggestion is to try connecting AngelNav to BoatBeacon and see what happens. If you only get the AIS data, then it means that they are indeed filtering out the instrument messages.
At the present time, AngelNav can only connect to a single source of NMEA data, though this could be added as a software enhancement at a later date.
Let us know how you get on!
Bill