Yes. It is valid that a given file may be both a Broadcast Wave (i.e., it has a BEXT chunk present), and conforms to a WAVEFORMATEX parameter configuration within the fmt chunk.
RIFF 'fmt ' chunk (16 bytes of data):
AudioFormat (SubDirectory) -->
+ [BinaryData directory, 16 bytes]
| Encoding = 1
| NumChannels = 1
| SampleRate = 96000
| AvgBytesPerSec = 288000
| BitsPerSample = 24
RIFF 'LIST_INFO' chunk (396 bytes of data):
Info (SubDirectory) -->
+ [Info directory, 396 bytes]
| Title = Given title of the recording
| Subject = Given subject of the recording
| Engineer = Digitized by JKP
| Copyright = Public Domain
| Artist = Name of the Artist
| Keywords = One, Or, More, Keywords
| Software = WaveLab 6.10
| DateCreated = 4/17/2008
| SourceForm = 1/4 in. tape
RIFF 'bext' chunk (602 bytes of data):
BroadcastExtension (SubDirectory) -->
+ [BinaryData directory, 602 bytes]
| Description = Broadcast description
| Originator = Broadcast originator
| OriginatorReference = Broadcast reference identifier
| DateTimeOriginal = 2008-04-17
| TimeReference = 0 0
| BWFVersion = 1
RIFF 'PAD ' chunk (11218 bytes of data):
Unknown_PAD =
RIFF 'data' chunk (266207226 bytes of data):
In this example above, the BEXT chunk is a separate part of the file. Its presence leads to fmt/2 being called out. Its presence is optional. The WAV file remains functional without it.
In this example above, the fmt chunk is a separate part fo the file. Its presence and particular configuration leads to fmt/142 being called out. Its presence is mandatory, but its configuration is one of at least three possible configurations. This specific configuration is fmt/142. Another configuration of it is fmt/143, for example.
This file is both fmt/2 and fmt/142.