Immutable assets should not be downloaded again on every visit. The useful question is not whether the idea sounds persuasive. It is whether it helps someone understand the work, make a decision, or complete a task with less friction.
What is happening
Images, fonts, and versioned styles are expensive compared with a small HTML response. Treating them all as temporary wastes time and bandwidth.
This tends to become visible at the boundary between the organization and the person encountering it for the first time. Internal familiarity hides effort that remains obvious to a customer, reader, applicant, or collaborator.
A practical response
Give versioned assets long cache lifetimes, use validators for documents, and keep development cache behavior separate from production.
The aim is a smaller, clearer system: one source for the record, one visible hierarchy, and one next action that behaves as expected. That approach improves the immediate page and makes later application or database work easier to add without rebuilding the public surface.