Does running a pruned node support the syncing of other nodes in the network? I decided to prune my Bitcoin core node to 25 GB. With the blocks that the node has in its data
directory (the ones that were not deleted), does such a node support the syncing of other nodes in the network? Moreover, let us imagine a new node that has just joined the network, let's say that has managed to download the first 10GB of data with his pruning set to 25GB. In such an early state, before pruning kicked in, does such a node serve the subset of the blocks that it has to the network?
Let the scope of this question be limited to the issue of syncing the blockchain data. I'm well aware of the advantages of using a pruned node as a wallet when compared to custodial services. There is already a question somewhat relevant to the matter and the answer to it suggests that as of May 2017, there is no way for pruned nodes to serve the subset of old blocks that they have. Is it still the case? Moreover, the answer to it does not refer to the second matter of serving a subset of blocks by a pruned node in which the pruning hasn't yet started.
Although I came across some resources and opinions on pruning, none of them elucidated the matter of syncing to me.
does such a node support the syncing of other nodes in the network?

Nodes that are pruned unset the NODE_NETWORK flag, which means that they don't advertise themselves as a potential source for block synchronization. Nodes won't consider peers without this flag as a potential source for downloading blocks.

In such an early state, before pruning kicked in, does such a node serve the subset of the blocks that it has to the network?

The same flag is not set here either. During sync most nodes are typically at 100% utilization and tend to behave very sluggishly, so they wouldn't be a particularly good source for anybody else.