The goal of the node would be to export its list of peers on an interval and publish it on IPNS to provide a dynamic bootstrap option for new peers. This helps if the static list published in a release gets deprecated.
Publishing to ipns seems doable with the offchain-ipfs feature. Where things are blurry is getting the list of peers from the chain.
I looked through the readme of sc_network and it mentions that the peerstore is being deprecated. If that is the case, how could one go about configuring a special node that can export it's list of connected peers on an interval? I suppose the "special" here could mean that only a well-known list of peerIDs are allowed to run this code, or other applicable access control methods.
From the little I know, substrate uses kademlia to manage connections. If that's the case, logic around filtering stale connections is already handled. In both cases though (is or is not kad), this list should be accessible in an environment where some comparison can be made with the current data on IPNS to perform some logic such as only publishing if the list changes.