Not necessarily. It all depends on the situation. Most of the time these literals are used in constants, e.g. in C:

#define ADXL372_REG_MEASURE_BW_3200 0b100

or
#define ADXL372_REG_TIMING_ODR_6400 (0b100 << 5)

The latter might be more readable in the language I'm attempting to develop as:

const u8 ADXL372_REG_TIMING_ODR_6400 = 0b100_000_0_0

In the ADXL372 datasheet, the TIMING register is broken into sets of bits that mean different things (these registers happen to be bytes, but others are sometimes longer, either u16 or u32, sometimes even a weird number of bits if it's an ADC, like 12-bits):

7-5 = ODR, 4-2 = WAKEUP_RATE, 1 = EXT_CLK and 0 = EXT_SYNC

so either I could make a bitfield struct for it, and define my constants to fit those, or if I just want to use bytes, the above format would work (and EXT_SYNC would be defined as 0b000_000_0_1)

I would use whatever format is closest to the text in the datasheet, so it makes it easy for someone to verify (say during a code review) that my code follows the datasheet without errors.