Comment # 7 on bug 1183568 from Michal Suchanek

then it's not kmod-static service what causes the delay.

(In reply to Felix Miata from comment #0)
> # systemd-analyze blame | head -n22
> 10.566s systemd-udev-trigger.service                          
> 10.385s systemd-modules-load.service                          
> 10.383s systemd-remount-fs.service                            
> 10.379s systemd-journald.service                              
> 10.190s dev-disk-by\x2dlabel-tvgp02swap.swap                  
> 10.161s modprobe@drm.service                                  
> 10.144s dev-hugepages.mount                                   
> 10.144s dev-mqueue.mount                                      
> 10.143s sys-kernel-debug.mount                                
> 10.142s sys-kernel-tracing.mount                              
> 10.131s modprobe@fuse.service                                 
> 10.125s modprobe@configfs.service                             
> 10.122s kmod-static-nodes.service                             

You can see here that there are many services that take about 10s, and most of
them are module related. I would suspect one of the drivers slows down the
boot.
Can you attach full dmesg?

Does systemd-remount-fs.service or dev-disk-by\x2dlabel-tvgp02swap.swap or
systemd-journald.service depend on kmod-static-nodes.service? If not even if
kmod-static-nodes.service is instanteous these other services will still
require time to complete.