Currently, beacon is included in the "other" category, which is an odd mixture of different resource types: beacon, ping, icon (are these favicons?), web application manifest, and ModelResource (I don't know what that is). You can already block ping specifically (as well as fetch and websocket, which are included in "raw" but not in "other), so it would also be nice to be able to block beacon specifically, without also blocking icons and manifests, for example.
<rdar://problem/124272237>