Brave doesn't implement WebSockets and WebRTC protections in the way Chrome has extended the LNA permission prompt. Instead, in addition to Shields restricting IP leaks, Brave added localhost resource protection to the web permission API: Localhost Resource Permission
Brave's per-site localhost permissions only handle HTTP/S and WebSockets. It hasn't yet incorporated WebRTC permission prompts like Chrome, but rather there is a privacy-focused WebRTC IP handling policy that allows you to dictate which IPs—public or private—are exposed through the protocol. This reduces the attack surface for rebinding and fingerprinting.