You are conflating two different concepts, so I'm not sure which you are talking about.
There are deflate blocks which use a static Huffman code, which are generally used when compressing very small amounts of data. Normally dynamic Huffman codes are used, where the code optimized for that particular block is sent at the start of the block. For small amounts of data, e.g. 100 bytes, the overhead of that code description would dominate the size of the output. Instead a static code would be used, which avoids the overhead at the cost of less compression. But overall, the result is smaller. All deflate applications (gzip, zlib, png, etc.) support all deflate block types.
The other concept is a pre-defined dictionary, which is a chunk of 32K of data that preloads the sliding dictionary in which matching strings are searched for. That is only supported by zlib. It is not possible to provide a pre-defined dictionary for a gzip stream. Your link for "deflate" is actually a link to the zlib format, which is where FDICT is defined.