The average person who's looking for "What can raytracing do for me" is going to get their answer from Control, Battlefield, Metro Exodus, or even the Quake II and Minecraft demos, and not some developer-centric Vulkan tutorial from Github.
Vulkan is a very low level API and even putting a single triangle on the screen is a huge wall of C++ code, so it's necessary to keep the domain part of the example as simple as possible.
As a graphics engineer, the more compelling use cases of ray tracing are things like visibility tests, which can be temporally stabilized by adding a low-discrepancy noise to each sample and used to perform leak-free global illumination. Samples can be used to feed other aspects of the pipeline like generating soft shadows, or atmospheric effects, etc.
It's an API tutorial, for professionals in the field. Ray tracing is just one tool in the toolbox, not the alpha and omega of how the frame gets composed.