More granular timestamp in DWH

[#1]

The existing time dimensions (day, hour, minute) in the DWH are not fine-granular enough for a few clients' use case.

Therefore, they are collecting the user-timestamp in milliseconds in a custom prop as a workaround for this issue.

But this workaround has some disadvantages:
a) User timestamp collected in the frontend is local and sometimes incorrect (days or years in the future/past)
b) For some server calls, the prop is not collected / missing
c) This workaround depends on the data collection (server-side timestamp would be independent of front-end data collection).

Can this be considered a possible enhancement, making the server-side hit timestamp available as a dimension in the data warehouse?

With my basic understanding, since DWH is the post-processed data. Any data on the DWH is the outcome of the raw data.
Hence, this particular enhancement should first be in the data feed because the current data feed shows second-level information.