@DorianCoding Welcome to the forum!
I guess that’s at least debatable. – For keeping a record of things, the creation date is not totally useless. (and e.g. knowing “creation date of passwords” is not the smallest feature request here, e.g. for expiration dates and “age reports”).
As far as I know, the public key doesn’t even get stored in Bitwarden. (i.e. not stored in the authenticator in general)
And what hash do you mean? (I’m not sure, hashing is even involved in the passkey registration and authentication ceremonies…)
Here in this post by @kpiris you can see how a passkey looks like in the Bitwarden data - and what get’s stored.
For most end-users (including me) almost everything you can see there wouldn’t be useful to see in the passkey field in the login item, I guess… [PS: Addition after @DorianCoding’s response: okay, maybe userName, userDisplayName or rpName (rp = relying part, i.e. the corresponding website) could be good to be able to see]
If we had the possibility to store multiple passkeys in one login item - let’s say at least two - I can imagine, it would be useful to be able to see which of the two “passkeys” would be the discoverable credential (= passkey in the strict definition) and which of the two would be the non-discoverable credential (= not a passkey in the strict definition). Because if you had to choose the credential for authentication, you had to choose the right one. (and even for registration, it would be nice to see, which kind of credential is already registered and which is “missing”…)