When single-transfer, ID-less memory-mapped semantics meet the required throughput, latency, outstanding and ordering contract, and the reduced interface is worth the implementation trade-off. Register/configuration paths are common examples, but the decision comes from traffic and system constraints rather than a rule about block names.
Common trap: Assuming Lite permits only one outstanding transaction or that no data mover may use it.